Menu
Set up and use Docker in Claude Code for Web environments. Use when Docker builds fail with bridge/iptables errors, SSL certificate errors through proxy, or when working in containerized web environments.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Sync this Claude Code config against new release notes — find config features added since the pinned baseline that this config should adopt. Use when Claude Code has been updated, when the user asks what's new / what changed / whether to adopt new settings or hooks, after a version bump, or when checking config currency against the latest release. Reports adoptable settings/hooks/env-vars/permissions as a risk-tiered proposal, then bumps the baseline. Do NOT use for auditing existing config quality, debugging hooks, or organizing rules — that is `maintaining-claude-code`.
Monitor and watch GitHub Actions CI/CD pipeline runs in real time. Use when the user has pushed code and wants to watch the build, check CI status, see if tests passed, monitor a pipeline, or wait for a workflow run to complete. Also use after any `jj git push` or `git push` command. Reports pass/fail with failed job logs. Do NOT use for writing or editing CI workflow YAML files, optimizing CI config, or debugging CI configuration — only for monitoring active runs.
Reorganize and clean up messy commit history on a feature branch into logical, reviewable commits. Use when cleaning up commits, preparing a branch for review, separating formatting from logic changes, fixing broken intermediate states, or squashing WIP commits.
Audit and improve Claude Code hooks, rules, and settings.json. Use when adding/debugging a hook, organizing rules, auditing settings.json (permissions, env vars, stale flags), or deciding between hook vs skill vs rule vs CLAUDE.md. For SKILL.md authoring use the skill-creator plugin; for CLAUDE.md audits use the claude-md-improver plugin.
Execute a structured test plan and emit a concise results document (JSON + Markdown). Use when running test plans, executing QA workflows, verifying acceptance criteria systematically, or producing test results documentation.
Search past Claude Code sessions to recall prior solutions, commands, fixes, and decisions. Use when the user references earlier work ("how did I fix", "last time we", "pick up where we left off", "a few months ago", "what was that … I set up", "didn't I once").
| name | using-docker-in-web |
| description | Set up and use Docker in Claude Code for Web environments. Use when Docker builds fail with bridge/iptables errors, SSL certificate errors through proxy, or when working in containerized web environments. |
| paths | ["**/Dockerfile*","**/docker-compose*.yml","**/docker-compose*.yaml","**/.dockerignore"] |
Claude Code for Web runs in a restricted container environment that requires special configuration for Docker.
You're in Claude Code for Web if:
# Proxy environment is set
echo $http_proxy # Shows a proxy URL
# Running inside a container
test -f /.dockerenv && echo "In container"
# iptables is restricted
iptables -L 2>&1 | grep -q "Permission denied"
# Install Docker
sudo apt-get update && sudo apt-get install -y docker.io
# Start daemon with restrictions (background)
sudo dockerd --iptables=false --bridge=none &
# Wait for daemon to be ready
sleep 3
# Verify
docker info
Standard builds fail because Docker tries to create bridge networks. Use these flags:
# Build with host networking and insecure SSL (for intercepting proxy)
csb build --host-network --insecure
What these flags do:
--host-network: Uses host networking instead of bridge (which requires iptables)--insecure: Adds -k to curl commands and disables npm strict-ssl (for SSL-intercepting proxies)Sandbox creation also needs host networking:
# When creating sandboxes, they'll run in the Docker network
# The proxy container won't work (needs iptables), so use --egress=all
csb create my-sandbox --egress=all
The daemon is trying to manage iptables rules. Restart with:
sudo pkill dockerd
sudo dockerd --iptables=false --bridge=none &
Same issue - daemon needs --bridge=none flag.
The proxy intercepts HTTPS. Use --insecure flag with csb build, or for manual curl:
curl -k https://example.com
npm config set strict-ssl false
npm install
npm config set strict-ssl true # Reset after
# 1. Install and start Docker
sudo apt-get update && sudo apt-get install -y docker.io
sudo dockerd --iptables=false --bridge=none &
sleep 3
# 2. Build csb images
csb build --host-network --insecure
# 3. Create a sandbox
csb create dev --egress=all
# 4. Connect
csb ssh dev
In Claude Code for Web:
# Stop all containers
docker stop $(docker ps -q) 2>/dev/null
# Stop daemon
sudo pkill dockerd