Run Claude Code in an isolated, hardened container with automatic credential injection.
3.5K
Run Claude Code inside an isolated, hardened Docker container — with automatic credential injection, a persistent package environment, and an optional file-exclusion system to keep secrets away from the AI.
Built on Ubuntu 24.04, the image goes through a strict hardening process at build time:
viber) is created and all subsequent layers run as that usernologin and its password is locked — root is unreachable from inside the container/home/linuxbrew/.linuxbrew, with Bun and GCC pre-installed/opt/linuxbrew-seed/ so a named Docker volume (secure-vibe-brew) can be initialized on first run without any root access — packages installed during a session survive container restartsThe image is meant to be used via the secure-vibe CLI (a Bun/TypeScript tool):
~/.claude.json, the macOS Keychain, or ~/.claude/.credentials.json, then injected into the container via an environment variable — nothing is written back to the host~/.claude host directory is mounted read-only--dangerously-skip-permissions — safe to use because it runs in an isolated container, not on your host system.env, secrets) from the container filesystem before Claude runs, using glob patterns — they are moved out before the container starts and restored after it exits--exclude flag to hide sensitive files from the container at runtime--save flag to zip or copy your project before Claude touches it~, /, /etc, /usr, etc.) are blocked from being mounted as the working directoryThe image is built and pushed to Docker Hub weekly via GitHub Actions, always tracking the latest version of Claude Code.
Content type
Image
Digest
sha256:8fce8a909…
Size
1.3 GB
Last updated
4 months ago
docker pull loice5/secure-vibe