| id | MCPX_DOCKER_DAEMON_DOWN |
|---|---|
| title | MCPX_DOCKER_DAEMON_DOWN |
| sidebar_label | DAEMON_DOWN |
| description | The Docker daemon is not reachable; isolated upstream servers cannot run. |
Severity: error Domain: Docker
A server is configured with isolation.enabled: true (or auto-detected as
needing isolation), but mcpproxy could not connect to the Docker daemon. The
upstream server cannot start without Docker.
- Docker Desktop is installed but not running (macOS / Windows).
- The Docker service hasn't been started (Linux:
dockerd,containerd). DOCKER_HOSTpoints to a stale socket (e.g. left over from a previous Colima session).- Permissions issue — see
MCPX_DOCKER_NO_PERMISSIONfor that variant.
docker info # works → daemon is up
docker context ls # which context (rootful, rootless, colima, …) is active
echo "$DOCKER_HOST" # should be empty or point at a real socketopen -a Docker # macOS Docker Desktop
colima start # macOS / Linux Colimasudo systemctl start docker
sudo systemctl enable docker # auto-start on bootIf you don't need isolation for a particular server, turn it off:
{ "isolation": { "enabled": false } }Note this means the upstream runs directly on the host with the host's
PATH / network — only do it for servers you trust.