-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Labels
Description
Description
All of the MCP servers installed via Docker MCP are throwing Can't start {X}: failed to connect: calling "initialize": EOF
Example of the errors:
~ docker mcp gateway run ✔ - Reading configuration... - Reading registry from registry.yaml - Reading catalog from [docker-mcp.yaml] - Reading config from config.yaml - Reading tools from tools.yaml - Reading secrets [obsidian.api_key postman.postman-api-key] - Configuration read in 527.649979ms - Those servers are enabled: fetch, node-code-sandbox, obsidian, playwright, postman - Listing MCP tools... - Running mcp/node-code-sandbox with [run --rm -i --init --security-opt no-new-privileges --cpus 1 --memory 2Gb --pull never -l docker-mcp=true -l docker-mcp-tool-type=mcp -l docker-mcp-name=node-code-sandbox -l docker-mcp-transport=stdio] - Running mcp/obsidian with [run --rm -i --init --security-opt no-new-privileges --cpus 1 --memory 2Gb --pull never -l docker-mcp=true -l docker-mcp-tool-type=mcp -l docker-mcp-name=obsidian -l docker-mcp-transport=stdio -e OBSIDIAN_API_KEY -e OBSIDIAN_HOST] - Running mcp/playwright with [run --rm -i --init --security-opt no-new-privileges --cpus 1 --memory 2Gb --pull never -l docker-mcp=true -l docker-mcp-tool-type=mcp -l docker-mcp-name=playwright -l docker-mcp-transport=stdio] - Running mcp/fetch with [run --rm -i --init --security-opt no-new-privileges --cpus 1 --memory 2Gb --pull never -l docker-mcp=true -l docker-mcp-tool-type=mcp -l docker-mcp-name=fetch -l docker-mcp-transport=stdio] - Running mcp/postman with [run --rm -i --init --security-opt no-new-privileges --cpus 1 --memory 2Gb --pull never -l docker-mcp=true -l docker-mcp-tool-type=mcp -l docker-mcp-name=postman -l docker-mcp-transport=stdio -e POSTMAN_API_KEY] > Can't start playwright: failed to connect: calling "initialize": EOF > Can't start postman: failed to connect: calling "initialize": EOF > Can't start obsidian: failed to connect: calling "initialize": EOF > Can't start fetch: failed to connect: calling "initialize": EOF > Can't start node-code-sandbox: failed to connect: calling "initialize": EOF > 0 tools listed in 1.25688583s - Using images: - mcp/fetch@sha256:ef9535a3f07249142f9ca5a6033d7024950afdb6dc05e98292794a23e9f5dfbe - mcp/node-code-sandbox@sha256:6b7180ab719dab2028dfc689002295ed6d55f7cc6217122d5025d849d5269666 - mcp/obsidian@sha256:0eba4c05742ad35faeb91eca40b792454d440d86449c9f1b3cb6c387a510651b - mcp/playwright@sha256:c0cd8718ba84f248ddda38c8e257afd1b996c56614d8ffe3366548db73ca158d - mcp/postman@sha256:effe3e8e8e138385797a0adf469de855bb8d9bbc74e0b1320b3b3658493ac2f6 > Images pulled in 43.752362ms - Watching for configuration updates... > Initialized in 1.828414326s > Start stdio serverReproduce
- Install Docker Desktop On Debian 12
- Install MCP Servers
- run
docker mcp gateway runto check the logs
Expected behavior
The MCPs should run.
docker version
Client: Docker Engine - Community
Version: 28.3.3
API version: 1.51
Go version: go1.24.5
Git commit: 980b856
Built: Fri Jul 25 11:34:00 2025
OS/Arch: linux/amd64
Context: desktop-linux
Server: Docker Desktop 4.46.0 (204649)
Engine:
Version: 28.4.0
API version: 1.51 (minimum version 1.24)
Go version: go1.24.7
Git commit: 249d679
Built: Wed Sep 3 20:57:37 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.27
GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0docker info
Client: Docker Engine - Community
Version: 28.3.3
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v1.9.11
Path: /home/ahmed/.docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.28.0-desktop.1
Path: /home/ahmed/.docker/cli-plugins/docker-buildx
cloud: Docker Cloud (Docker Inc.)
Version: v0.4.27
Path: /home/ahmed/.docker/cli-plugins/docker-cloud
compose: Docker Compose (Docker Inc.)
Version: v2.39.2-desktop.1
Path: /home/ahmed/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.42
Path: /home/ahmed/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Docker Inc.)
Version: v0.2.0
Path: /home/ahmed/.docker/cli-plugins/docker-desktop
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.31
Path: /home/ahmed/.docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: /home/ahmed/.docker/cli-plugins/docker-init
mcp: Docker MCP Plugin (Docker Inc.)
Version: v0.18.0
Path: /home/ahmed/.docker/cli-plugins/docker-mcp
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /home/ahmed/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.18.3
Path: /home/ahmed/.docker/cli-plugins/docker-scout
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 4
Server Version: 28.4.0
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Discovered Devices:
cdi: docker.com/gpu=webgpu
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da
runc version: v1.2.5-0-g59923ef
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.10.14-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 7.654GiB
Name: docker-desktop
ID: 676bff14-751f-435a-bdf1-bd40826f5dd4
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=unix:///home/ahmed/.docker/desktop/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
::1/128
127.0.0.0/8
Live Restore Enabled: falseDiagnostics ID
_
Additional Info
No response
DigitallyBorn