HolyClaude tackles a pain point almost every AI developer using Docker has faced: containerizing multiple AI command-line interfaces and their complex dependencies isn’t straightforward. You can spend hours wrestling with shared memory limits, display configuration, UID permission mismatches, or SQLite locks on network drives. HolyClaude wraps Claude Code, a CloudCLI web UI, seven AI CLIs, a headless Chromium browser, and over fifty developer tools into a single Docker container that smooths out these rough edges.
How HolyClaude bundles AI tooling into a unified Docker container
At its core, HolyClaude is an AI development workstation packaged as a Docker container. It includes Claude Code — an AI orchestration engine — paired with a CloudCLI web interface for accessible management. Inside the container, you’ll find seven AI CLIs: Gemini, Codex, Cursor, TaskMaster, Junie, and OpenCode, among others. These CLIs cover a range of AI coding and interaction needs under one roof.
To support browser-based tasks, HolyClaude bundles a headless Chromium browser running under Xvfb (a virtual framebuffer) and automated with Playwright. This setup is notoriously tricky in Docker due to graphical environment and shared memory constraints.
The container management uses s6-overlay, a process supervisor that helps run multiple services properly inside a container.
Architecturally, HolyClaude is designed for both AMD64 and ARM64 platforms, broadening compatibility across desktop and server hardware. It integrates with Anthropic AI subscriptions via OAuth or API keys, storing credentials securely in bind-mounted volumes external to the container.
The project offers two variants: a full version with all tools and a slimmed-down version to reduce resource use.
Why HolyClaude stands out: solving Docker integration edge cases
What makes HolyClaude more than a simple Docker container is its careful handling of multiple Docker-specific challenges that typically cause major headaches:
Chromium shared memory limits: Docker containers have default shared memory size limits that cause Chromium to crash or misbehave. HolyClaude configures these limits appropriately.
Xvfb display setup: Running a headless X server inside Docker requires precise configuration to avoid display errors. HolyClaude automates this.
UID permission mapping: File permission mismatches between host and container users can lock you out of volumes or cause install scripts to hang. HolyClaude manages UID and GID mapping to ensure permissions align.
Claude Code installer hang: Running the installer in a root-owned WORKDIR causes hangs; the container avoids this by adjusting ownership and working directories.
SQLite locks on NAS mounts: Network-attached storage can cause SQLite to lock improperly inside containers. HolyClaude implements workarounds to mitigate this.
Multi-service supervision: s6-overlay helps run Claude Code, web UI, Chromium, and AI CLIs reliably within one container.
Addressing these edge cases results in a containerized AI workstation that “just runs” without hours of manual tweaking. This battle-hardened approach sets HolyClaude apart from DIY container setups that often break or require deep Docker expertise.
The code quality reflects practical experience: the container scripts and overlays are tailored for robustness and DX, not theoretical elegance. This means tradeoffs like increased image size or complexity are accepted to prioritize a smooth out-of-the-box experience.
Quick start with HolyClaude
Here is the exact quick start from the project README:
# 1. Create a folder for HolyClaude:
mkdir holyclaude && cd holyclaude
# 2. Create a docker-compose.yaml file. Copy one of the templates provided:
# - Quick template — minimal, zero config, just works
# - Full template — all options, fully documented
# 3. Pull and start the container:
docker compose up -d
# 4. Open the web UI:
# http://localhost:3001
# 5. Create a CloudCLI account (takes 10 seconds), sign in with your Anthropic account, and you're live.
The project emphasizes no .env files or heavy pre-configuration. It aims to get you running within 30 seconds.
For network exposure, it advises against traditional port forwarding and recommends using Tailscale or Cloudflare Tunnel for secure remote access.
who HolyClaude is for and tradeoffs to consider
HolyClaude is ideal for AI developers and enthusiasts who want a ready-to-go AI development environment inside Docker without the usual setup headaches. If you’re juggling multiple AI CLIs and need browser automation, it bundles everything into a single container that works on common hardware architectures.
The main tradeoffs are the container’s complexity and footprint. Bundling 50+ tools and multiple AI CLIs results in a sizeable image, which may not suit minimal or resource-constrained environments.
Also, the container targets the Anthropic Claude Code ecosystem; if your workflow relies heavily on other providers or custom local LLMs, integration may require additional work.
Because it handles many Docker edge cases internally, HolyClaude sacrifices some configurability for simplicity. Advanced users wanting granular control over each component might find this limiting.
Overall, HolyClaude stands out as a practical, no-nonsense solution that reduces AI workstation setup from hours to seconds. It’s worth understanding even if you don’t adopt it, as it demonstrates how to tackle real Docker quirks in AI tooling containers with reliability and developer experience in mind.
→ GitHub Repo: CoderLuii/HolyClaude ⭐ 2,206 · Dockerfile