Claude-in-container

Always-on Claude Code in a Docker or Podman container, reachable from your phone or browser via Remote Control.

  • AI
  • Productivity
  • Tools & Utilities
Always-on Claude Code in a Docker or Podman container, reachable from your phone or browser via Remote Control. Claude has scoped access to a single mounted data folder, keeping host files, SSH keys, and cloud credentials isolated. Runs non-root with no sudo, so a bad command hits the container, not your host. For homelab users who want a sandboxed, self-hosted Claude Code experience without exposing system-level access.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

44/100 Fair

Maintained
78last commit 39 days ago
Popular
61 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
1
Open issues
11
Last commit
2026-10-13
Latest release
v2.1.296
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (ganesh35/claude-in-container)

Resources & Compatibility

Minimum requirements: 4 GB RAM.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Run a setup check after first start After you first start the app, run /doctor to check installation health, find unused add-ons, and get suggested fixes. It reports what it found and asks before changing anything, so you can catch setup problems before they break the app. source
  • Fix install folder permissions if needed If you see permission errors, run sudo mkdir -p ~/.local/bin and sudo chown -R $(whoami) ~/.local in a terminal. This creates the install folder and makes sure your user can write to it, so the app won’t get stuck updating or saving files. source
  • Use guided self-hosted setup if needed If you are setting up self-hosted runners, workers that run on your own machines, log in with an Owner role and run claude self-hosted-runner setup. The guided session creates the environment, registers secrets, and verifies the setup so missing pieces do not fail later. source
  • Create the Data folder before first start Create the Data folder owned by the container user in Extra Parameters (default --user 99:100), e.g. mkdir -p DIR && chown 99:100 DIR. source
  • Connect on first start Open the console or run docker exec -it claude-in-container tmux new -A -s main, then log in with your Claude subscription. source
  • Sharing one Data folder across containers Several containers can share one Data folder: give each its own name and set Continue to false on all but one. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to open ports or add a reverse proxy to reach it from a phone or browser?

No. Remote Control connects outbound to claude.ai and nothing listens on your network. You can use phone and browser access through Remote Control in the Claude app or claude.ai/code.

What host access and secrets does Claude get inside the container?

It sees only the one mounted data folder and runs non-root with no sudo. It gets only the keys and tokens you pass in .env or a mount.

Where do I back up data, and how do I move or remove the setup?

Projects, login, settings, history, and tools live in one folder, so copy that folder to move to another host. For clean removal, delete the container and its folder.

What Unraid permission should I check before first start?

Create the Data folder before first start and make it owned by the container user 99:100. The Extra Parameters default is --user 99:100.

Does it keep running when my SSH session or host reboots?

Claude runs in tmux, so closing a terminal or losing SSH does not stop it. The restart policy brings the container back after crashes or reboots, and the last conversation resumes after a restart.

Does it automatically update Claude Code?

No, the auto-updater is off. You choose when to move to a new Claude Code version, and you can roll back by rebuilding the previous one.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads