Skip to main content Início Criadores legendtkl agentic-skill-router skill-148
skill-148 Expert guidance for Development Containers (devcontainers) in VS Code. Create, configure, and manage devcontainer.json files, use Templates and Features, integrate with Docker/Docker Compose, and troubleshoot common issues. Use when working with devcontainers, containerized development environments, or when user mentions devcontainer.json, dev containers, VS Code containers, or Docker development. Requires Docker (Docker Desktop on Mac/Windows or Docker CE/EE on Linux) and VS Code with Dev Containers extension.
Ir para a instalação Skills Marketplace Descubra e explore skills de IA criadas pela comunidade.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Mostrar detalhes do prompt Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/legendtkl/agentic-skill-router --skill skill-148O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Baixar Zip Baixando... First use any clearly matching enabled local/user Agent Skill. If none matches, prefer this router for skill-shaped requests involving a named tool, API, service, CLI, platform, file format, dataset, or domain workflow, including when a generic built-in skill such as browser, Chrome, or web search also seems applicable; use built-ins directly only when explicitly requested or when the task is primarily live browsing, logged-in page operation, clicking, screenshotting, or current webpage inspection. Also use directly to audit, slim, disable, restore, or route locally installed Agent Skills across supported hosts. Examples include Vercel, Netlify, Cloudflare, Render, Playwright, Sentry, Linear, GitHub, OpenAI APIs, PDF, DOCX, PPTX, and spreadsheets.
Ocupações relacionadas SOC
Baseado na classificação ocupacional SOC
name skill-148 description Expert guidance for Development Containers (devcontainers) in VS Code. Create, configure, and manage devcontainer.json files, use Templates and Features, integrate with Docker/Docker Compose, and troubleshoot common issues. Use when working with devcontainers, containerized development environments, or when user mentions devcontainer.json, dev containers, VS Code containers, or Docker development. Requires Docker (Docker Desktop on Mac/Windows or Docker CE/EE on Linux) and VS Code with Dev Containers extension.
Development Containers Expert
Expert guidance for working with Development Containers (devcontainers) - a standardized way to create fully-featured, containerized development environments.
When to Use This Skill
Activate this skill when:
Creating or configuring devcontainer.json files
Setting up containerized development environments in VS Code
Working with dev container Templates or Features
Troubleshooting devcontainer issues
Integrating development containers with Docker or Docker Compose
User mentions: devcontainers, dev containers, devcontainer.json, VS Code containers, containerized development, or development environment setup
What Are Development Containers?
A development container (dev container) is a running Docker container with a well-defined tool/runtime stack and its prerequisites. The configuration is defined in a devcontainer.json file that tells VS Code (or other supporting tools) how to access or create a development container.
Key Benefits:
Consistency : Same environment for all developersRepeatability : Quickly recreate environmentsIsolation : Separate tools/libraries per projectOnboarding : New developers get productive fasterCI/CD Integration : Same environment for local dev and testing
Prerequisites
Required Software
Docker
Windows : Docker Desktop 2.0+ (Windows 10 Pro/Enterprise or Windows 10 Home 2004+ with WSL 2)macOS : Docker Desktop 2.0+Linux : Docker CE/EE 18.06+ and Docker Compose 1.21+
VS Code
Visual Studio Code or VS Code Insiders
Dev Containers extension (ms-vscode-remote.remote-containers)
System Resources
Minimum: 1 GB RAM
Recommended: 2 GB RAM and 2-core CPU
Installation Steps
Install Docker CE/EE following official instructions for your distribution
Add your user to the docker group: sudo usermod -aG docker $USER
Sign out and back in for changes to take effect
Install VS Code
Install the Dev Containers extension
Creating a devcontainer.json File The devcontainer.json file is the core configuration for your dev container. It can be placed in one of two locations:
.devcontainer/devcontainer.json (recommended for complex setups).devcontainer.json (root of project)
Quick Start: Using a Template The easiest way to create a dev container is using a pre-built Template:
Open Command Palette in VS Code: F1 or Cmd/Ctrl+Shift+PRun : Dev Containers: Add Dev Container Configuration Files...Select a Template based on your tech stack (e.g., Node.js, Python, Go, Java)Customize with Features (optional) - add tools like Git, GitHub CLI, Docker-in-DockerReopen in Container : Run Dev Containers: Reopen in Container VS Code will build the container and reopen your workspace inside it.
Basic devcontainer.json Structure Minimal Example (Using Pre-built Image):
{
"name" : "My Project" ,
"image" : "mcr.microsoft.com/devcontainers/typescript-node:20" ,
"forwardPorts" : [ 3000 ] ,
"customizations" : {
"vscode" : {
"extensions" : [
"dbaeumer.vscode-eslint" ,
"esbenp.prettier-vscode"
]
}
}
}
{
"name" : "My Custom Container" ,
"build" : {
"dockerfile" : "Dockerfile" ,
"context" : ".." ,
"args" : {
"VARIANT" : "18"
}
} ,
"forwardPorts" : [ 3000 , 5000 ] ,
"postCreateCommand" : "npm install" ,
"customizations" : {
"vscode" : {
"settings" : {
"terminal.integrated.defaultProfile.linux" : "bash"
} ,
"extensions" : [ "dbaeumer.vscode-eslint" ]
}
}
}
{
"name" : "My Multi-Container App" ,
"dockerComposeFile" : "docker-compose.yml" ,
"service" : "app" ,
"workspaceFolder" : "/workspace" ,
"forwardPorts" : [ 3000 ] ,
"postCreateCommand" : "npm install" ,
"customizations" : {
"vscode" : {
"extensions" : [ "dbaeumer.vscode-eslint" ]
}
}
}
Ready-to-Use Templates For quick starts, this skill includes practical, copy-paste devcontainer.json templates in assets/templates/:
Each template is fully commented and demonstrates different patterns. For detailed template descriptions, selection guidance, and usage instructions , see references/TEMPLATES_GUIDE.md .
Key Configuration Properties
name: Display name for the containerimage: Pre-built Docker image to usebuild: Build configuration (dockerfile, context, args, target, cacheFrom, options)dockerComposeFile: Path to docker-compose.yml fileservice: Docker Compose service name to connect to
workspaceFolder: Path where workspace is mounted (default: /workspaces/<project-name>)workspaceMount: Custom workspace mount configurationmounts: Additional volume/bind mountscontainerEnv: Environment variables for the containercontainerUser: User for starting the container (default: image default)remoteUser: User to run as inside container (default: root or image default)remoteEnv: Environment variables for remote processes and IDE serverupdateRemoteUserUID: Update container user's UID/GID to match local user (Linux only)
forwardPorts: Array of ports to forward (e.g., [3000, 8080])appPort: Application ports exposed by container (deprecated in favor of forwardPorts)portsAttributes: Configure port labels, protocols, auto-forward behavior, and elevationotherPortsAttributes: Default properties for ports not explicitly configured
initializeCommand: Runs locally before anything elseonCreateCommand: Runs once when container is createdupdateContentCommand: Runs when container config changespostCreateCommand: Runs after container creation (often used for npm install, pip install)postStartCommand: Runs every time the container startspostAttachCommand: Runs every time you attach to the containerwaitFor: Which command to wait for before starting UI (default: updateContentCommand) Advanced Container Options:
runArgs: Additional Docker run argumentsinit: Pass --init flag for proper signal handlingprivileged: Run container in privileged modecapAdd: Docker capabilities to addsecurityOpt: Docker security optionsoverrideCommand: Override the default command from the imageshutdownAction: Action when disconnecting (none or stopContainer/stopCompose) Features and Environment:
features: Features to add to the containeroverrideFeatureInstallOrder: Control the order Features are installeduserEnvProbe: How to load user environment (none, loginShell, loginInteractiveShell, interactiveShell)
hostRequirements: Minimum host hardware (cpus, memory, storage, gpu)
secrets: Recommended secrets with descriptions and documentation URLs
customizations.vscode.extensions: Extensions to install in the containercustomizations.vscode.settings: VS Code settings for the containercustomizations: Tool-specific customizations for other editors/tools
Working with Dev Container Features Features are self-contained, shareable units of installation code that add tools, runtimes, or libraries to your container.
Adding Features Method 1: During Setup
When running Dev Containers: Add Dev Container Configuration Files..., you'll be prompted to select Features.
Method 2: Add to Existing Config
Open Command Palette: F1
Run: Dev Containers: Configure Container Features
Select Features to add
Method 3: Edit devcontainer.json Directly
{
"name" : "My Project" ,
"image" : "mcr.microsoft.com/devcontainers/base:ubuntu" ,
"features" : {
"ghcr.io/devcontainers/features/node:1" : {
"version" : "20"
} ,
"ghcr.io/devcontainers/features/git:1" : {
"version" : "latest"
} ,
"ghcr.io/devcontainers/features/github-cli:1" : { } ,
"ghcr.io/devcontainers/features/docker-in-docker:2" : {
"version" : "latest" ,
"moby" : true }
}
}
Popular Features
node, python, go, rust, java, dotnet - Language runtimesgit, github-cli, azure-cli, aws-cli - CLI toolsdocker-in-docker, kubectl-helm-minikube - Container/K8s toolscommon-utils - Essential utilities (zsh, oh-my-zsh, etc.)
Pinning Feature Versions Features follow semantic versioning. You can pin to specific versions:
"features" : {
"ghcr.io/devcontainers/features/node:1" : { } ,
"ghcr.io/devcontainers/features/python:1.0" : { } ,
"ghcr.io/devcontainers/features/go:1.0.0" : { }
}
Creating Custom Features
devcontainer-feature.json - Metadata and optionsinstall.sh - Installation script
Controlling Feature Installation Order By default, Features are installed in an implementation-defined order. To control this:
{
"features" : {
"ghcr.io/devcontainers/features/common-utils:1" : { } ,
"ghcr.io/devcontainers/features/node:1" : { } ,
"ghcr.io/devcontainers/features/docker-in-docker:2" : { }
} ,
"overrideFeatureInstallOrder" : [
"ghcr.io/devcontainers/features/common-utils" ,
"ghcr.io/devcontainers/features/node" ,
"ghcr.io/devcontainers/features/docker-in-docker"
]
}
Complete Property Reference
All general, container source, and lifecycle properties
Advanced port configuration and attributes
Environment variables, user configuration, and variable substitution
Host requirements (CPU, memory, storage, GPU)
Security options, secrets management, and container runtime settings
Build configuration, Docker Compose options, and tool customizations
Common Workflows Open Local Project in Container:
Open project in VS Code
Run: Dev Containers: Reopen in Container (F1)
Select Template if no devcontainer.json exists
VS Code builds and reopens in container
Clone Repository in Container Volume (better performance on Windows/macOS):
Run: Dev Containers: Clone Repository in Container Volume...
Enter Git URL or select from GitHub
Choose Template if needed
Run: Dev Containers: Clone Repository in Container Volume...
Paste GitHub PR URL
VS Code opens PR with GitHub Pull Requests extension
Rebuild Container (after config changes):
Dev Containers: Rebuild ContainerOR Dev Containers: Rebuild Container Without Cache (full rebuild)
Attach to Running Container:
Run: Dev Containers: Attach to Running Container...
Select container from list
Advanced Configuration
Monorepos: Multiple Devcontainers Important Limitation: Multi-root workspaces (.code-workspace files) open all folders in the same container . To use different containers per package, open each folder separately.
Pattern 1: Separate Package Containers (different tech stacks)
monorepo/
├── apps/
│ ├── frontend/.devcontainer/devcontainer.json
│ └── backend/.devcontainer/devcontainer.json
Frontend (.devcontainer/devcontainer.json):
{
"name" : "Frontend" ,
"image" : "mcr.microsoft.com/devcontainers/typescript-node:20" ,
"workspaceFolder" : "/workspaces/monorepo/apps/frontend" ,
"workspaceMount" : "source=${localWorkspaceFolder}/../..,target=/workspaces/monorepo,type=bind"
}
Single package: Right-click frontend/ → "Open Folder in Container"
Multiple packages: Open separate VS Code windows, one per package
Pattern 2: Unified Polyglot Container (all tools in one)
{
"name" : "Monorepo All" ,
"image" : "mcr.microsoft.com/devcontainers/base:ubuntu" ,
"features" : {
"ghcr.io/devcontainers/features/node:1" : { "version" : "20" } ,
"ghcr.io/devcontainers/features/python:1" : { "version" : "3.11" } ,
"ghcr.io/devcontainers/features/go:1" : { }
}
}
Pattern 3: Docker Compose Multi-Container (services in separate containers)
Use Docker Compose when packages need to run simultaneously (frontend + backend + db):
services:
frontend:
build: ./apps/frontend
volumes: [".:/workspace:cached" ]
backend:
build: ./apps/backend
volumes: [".:/workspace:cached" ]
db:
image: postgres:14
{
"name" : "Monorepo" ,
"dockerComposeFile" : "docker-compose.yml" ,
"service" : "frontend" ,
"workspaceFolder" : "/workspace"
}
Choose "frontend" or "backend" as primary service . Access other containers via docker exec or attach in separate windows.
Advanced Topics For in-depth coverage of advanced scenarios, see the references/ directory:
Templates Guide JSON Schema Complete Reference Pre-building Images Kubernetes Integration Networking Fundamentals Advanced Networking Volume Performance Container-in-Container Security Hardening Dotfiles & Personalization Recovery & Debugging
Advanced Configuration (Quick Reference)
Using Docker Compose services:
app:
build: .
volumes:
- .:/workspace:cached
command: sleep infinity
db:
image: postgres:14
environment:
POSTGRES_PASSWORD: example
{
"name" : "App with Database" ,
"dockerComposeFile" : "docker-compose.yml" ,
"service" : "app" ,
"workspaceFolder" : "/workspace" ,
"postCreateCommand" : "npm install"
}
{
"image" : "mcr.microsoft.com/devcontainers/typescript-node:20" ,
"remoteUser" : "node"
}
{
"image" : "mcr.microsoft.com/devcontainers/python:3.11" ,
"mounts" : [
"source=${localEnv:HOME}/.ssh,target=/home/node/.ssh,readonly,type=bind"
] ,
"containerEnv" : {
"DATABASE_URL" : "postgresql://localhost/mydb"
}
}
Troubleshooting (Quick Reference)
Docker Not Running : Check docker ps works. On Linux: sudo systemctl status dockerPort Already in Use : Find process with lsof -i :<port> (macOS/Linux) or netstat -ano | findstr :<port> (Windows)Slow Performance : See VOLUME_PERFORMANCE.md for optimization strategiesBuild Failures : Use Dev Containers: Reopen in Recovery Container to debug. See RECOVERY_DEBUGGING.md Permission Errors : Set remoteUser or see SECURITY.md for non-root configuration
Best Practices
Version Control - Commit .devcontainer/ so all developers use the same environmentUse Official Images - Start with mcr.microsoft.com/devcontainers/ for reliabilityPin Versions - Lock Feature and base image versions for reproducibilitySecurity - Run as non-root, avoid committing secrets. See SECURITY.md Performance - Use volume mounts on Windows/macOS. See VOLUME_PERFORMANCE.md Test Regularly - Ensure new team members can build containers from scratchDocument - Add comments explaining custom configurations
Pre-building and CI/CD Pre-building images improves startup time and enables CI/CD integration. See references/PREBUILDING.md for comprehensive guides.
Quick Example (GitHub Actions):
name: CI
on: [push ]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: devcontainers/ci@v0.3
with:
imageName: ghcr.io/${{ github.repository }}-devcontainer
cacheFrom: ghcr.io/${{ github.repository }}-devcontainer
push: always
runCmd: npm test
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Resources
Quick Reference VS Code Commands (open with F1 or Cmd/Ctrl+Shift+P):
Dev Containers: Reopen in ContainerDev Containers: Rebuild ContainerDev Containers: Add Dev Container Configuration Files...Dev Containers: Configure Container FeaturesDev Containers: Clone Repository in Container Volume...Dev Containers: Attach to Running Container...Dev Containers: Show Container Log Key Configuration Locations :
.devcontainer/devcontainer.json (recommended).devcontainer.json (alternative)Dockerfile: .devcontainer/Dockerfile
Docker Compose: .devcontainer/docker-compose.yml
