Practical overview
When it fits
Use it when you need a repeatable Docker-based workspace for web3 development or smart-contract security work and want to select a configuration suited to the task.
Who it is for
- Web3 developers who want a prepared workspace with Foundry, Hardhat or basic Solidity support.
- Smart-contract auditors and security researchers who need an environment with analysis and fuzzing tools.
- Developers who want to choose between streamlined and more security-hardened container configurations.
Documented uses
- Set up a containerized Foundry and Hardhat workspace.
- Create an audit workspace with Slither, Mythril, Crytic-compile and Echidna.
- Select a configuration with security hardening measures such as capability dropping, AppArmor and tmpfs mounts.
- Open a prepared development container locally in VS Code or use the listed Codespaces configuration.
Requirements & limits
The documented local setup requires Visual Studio Code, Microsoft's Dev Containers extension, Docker and Docker Buildx. The README also lists a prebuilt GitHub Codespaces configuration.
- The Auditor variant includes Slither, Mythril, Crytic-compile, Foundry, Hardhat and Echidna, plus Docker-in-Docker.
- Minimal focuses on Foundry, Hardhat, basic Solidity support and essential Python tools.
- Hardened maintains network connectivity and lists capability dropping, AppArmor, no-new-privileges and tmpfs workspace hardening.
- The Air-gapped variant's listed bridge networking does not isolate network access by default.
- The README cautions that devcontainers and VS Code do not eliminate host-security risks.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up a local Devcontainer workspace
Build and open one of the project's development-container variants in VS Code.
Before you start
- Visual Studio Code
- Microsoft Dev Containers extension
- Docker and Docker Buildx installed on the local operating system
- Docker service running and user access to Docker
Steps
Clone the repository and navigate to the preferred variant folder under .devcontainer.
Open that variant folder in VS Code.
Select “Reopen in Container” and wait for the container volume to build.
For first-time setup, press Enter at the prompted console log to trigger the terminal.
Expected outcome
A development workspace built from the selected container variant.
Guide limitations
- The project warns that devcontainers are not fully secure environments.
- VS Code may expose host command execution or shared signing sockets such as gpg-agent.
- The listed Air-gapped configuration uses bridge networking and does not provide network isolation by default.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- theredguild/devcontainer · Official homepage title · retained in its source language