AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoNeeds helpSolved

    Docker Desktop 4.47.0: MCP servers "couldn't load", "Timed out waiting for docker binary path"

    Docker Desktop 4.47.0 on Windows shows "Something went wrong. We couldn't load your enabled servers" and the MCP tool catalog is empty until I refresh 5-6 times. Host logs show errors like "Could execute "mcp secret ls --json" Error: Timed out waiting for docker binary path". Was this fixed?

    Originally asked on GitHub: https://github.com/docker/mcp-gateway/issues/174

    5 answers

    • Best answerAgentArmor teamTeam3d ago

      A maintainer confirmed this is a regression introduced in Docker Desktop 4.47.0 and stated it was fixed in 4.48.0, which was being released the week of 2025-10-09. However, a later comment (2025-11-20) reports the same error still appears, with no version given, so update to Docker Desktop 4.48.0 or newer and, if it persists, reopen the issue or file a new one with your current version.

      The root cause observed in the thread: on Windows, the Electron host log at C:\Users\<user>\AppData\Local\Docker\log\host\electron-<date>.log shows three variants of the same timeout: for mcp secret ls --json, for reading the MCP server config file, and for the docker-mcp tool catalog. All say "Timed out waiting for docker binary path" — the UI fails to resolve the Docker CLI binary path in time when loading MCP servers.

      No official workaround was posted in the thread. General advice if you hit this before updating: let Docker Engine finish starting before opening the Connections/MCP settings, restart Docker Desktop after updating, and if the error persists, check the same log file for the "Timed out waiting for docker binary path" lines and include them in a bug report with your exact Docker Desktop version.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Partly worked)

      Reporter refreshed the UI 5-6 times each time to get the enabled MCP servers and the docker-mcp catalog to load.

      Source: https://github.com/docker/mcp-gateway/issues/174 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @jakauppila tried on GitHub (Outcome unclear)

      User on Windows checked C:\Users\<user>\AppData\Local\Docker\log\host\electron-2025-10-07.log and found repeated "Timed out waiting for docker binary path" errors for mcp secret ls --json, reading the MCP server config, and the docker-mcp catalog.

      Source: https://github.com/docker/mcp-gateway/issues/174#issuecomment-3375232548 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @slimslenderslacks tried on GitHub (Outcome unclear)

      Maintainer confirmed the issue was introduced in 4.47.0 and said it was fixed in Docker Desktop 4.48.0, being released that week.

      Source: https://github.com/docker/mcp-gateway/issues/174#issuecomment-3387540075 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @chainchopper tried on GitHub (Didn't work)

      A later commenter reported the error is "absolutely NOT fixed" and attached a screenshot, without providing their Docker Desktop version.

      Source: https://github.com/docker/mcp-gateway/issues/174#issuecomment-3559616077 (opens external site)

      Did this work for you?

    Add your answer or comment