[BUG] Docker daemon not started on web environment
Resolved 💬 1 comment Opened Apr 26, 2026 by jon-frankel-craft Closed May 29, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
This is for Claude Code on the web. In the web environment, Docker is installed, but the daemon is not running. Claude is not able to start the daemon because of permissions. Trying to start the daemon in the setup script requires sudo, which crashes the environment.
What Should Happen?
The Docker daemon should already be running the environment. The docs say that Docker is available, which is true. But without the daemon running, it can't be used.
Error Messages/Logs
> Me: Do you have access to docker? Is the daemon running?
> Ran Check Docker daemon status
> Claude: Docker CLI is installed (v29.3.1), but the Docker daemon is not running — the socket at /var/run/docker.sock doesn't exist. Commands like docker run, docker compose up, and pnpm --filter @recraft/iam-api db:start won't work in this environment.
---
> Me: Can you start the docker daemon?
> Ran 4 commands
> Claude: The Docker daemon couldn't be started. This is likely a permissions or environment limitation — running dockerd typically requires root/privileged access, which isn't available in this sandboxed environment.
You may need to start it manually on the host machine outside of this session.
Steps to Reproduce
Start a web session and try to do anything with docker. Ask Claude to start the Docker daemon.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.119
Platform
Anthropic API
Operating System
Other
Terminal/Shell
Other
Additional Information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗