OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

WEB3 Dev Containers

A public MIT-licensed repository providing Docker-based isolated environments for running Web3 development code.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

WEB3 Dev Containers — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it before running unfamiliar repositories, suspicious packages or smart-contract code, or when a Docker-based Web3 workspace is preferable to direct host execution.

Who it is for

  • Web3 developers working with Ethereum, Solana, Foundry, Moccasin, Solidity or Vyper tooling.
  • Auditors inspecting unfamiliar smart-contract repositories or packages.
  • Users seeking disposable or isolated development workspaces.

Documented uses

  • Run unfamiliar Web3 code with reduced exposure to the host environment.
  • Create Docker-based workspaces for documented Web3 development stacks.
  • Open a hardened Claude development container with selected credentials and network access.
  • Choose between unmounted ephemeral work and mounted persistent project work.
Before you choose

Requirements & limits

The repository is publicly accessible and MIT licensed. Docker is required for the documented workflows; some paths additionally require the devcontainer CLI, VS Code and its Dev Containers extension, or WSL on Windows.

  • The project distinguishes the hardened, lair-ready Claude stack from the original stacks, which lack the same documented firewall, scoped-sudo and lair support.
  • Unmounted containers are recommended in the documentation for untrusted code, while mounted containers persist work to the host.
  • Credentials and selected network access are opt-in in the documented Claude workflow.
  • The project is implemented primarily in Shell and is designed around Docker, CLI and self-hosted use.
  • Container isolation reduces exposure but is explicitly not a fail-safe.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up the documented Claude container workflow

Install the repository and lair CLI so a Claude development container can be opened.

Before you start

  • Docker must be installed and running.
  • The devcontainer CLI is required.
  • The repository documents npm installation for @devcontainers/cli.
  • The ~/.local/bin directory should be on PATH.

Steps

  1. Install the devcontainer CLI with npm install -g @devcontainers/cli.

  2. Clone the repository to ~/web3-dev-containers.

  3. Run ~/web3-dev-containers/lair self-install.

  4. Start a Claude container with lair claude, or use lair mounted claude for a project whose work persists to the host.

  5. If the editor does not open automatically, use Reopen in Container; otherwise use the headless shell.

Expected outcome

A Claude stack is opened in an isolated container, with unmounted ephemeral use available by default and mounted use available when selected.

Guide limitations

  • The documentation states that only the Claude stack is hardened and lair-ready.
  • The repository explicitly says container isolation is not fail-safe.
  • The container starts logged out; Claude login is performed inside the container when needed.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
1 October 2026
Original website title
Cyfrin/web3-dev-containers · Official homepage title · retained in its source language
How we review sourcesSuggest a correction