mcp-proxy Docker on AMD64: "no matching manifest for linux/amd64"

3 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Fixed for the reporter by using a newer tag: v0.3.2-alpine failed to pull on the AMD64 host, and v0.4.1-alpine pulled and ran successfully. The thread does not state that a manifest was explicitly added; it only reports that the newer tag works.

  The maintainer suggested pulling from Docker Hub:

  Copy to clipboard

  docker pull sparfenyuk/mcp-proxy:v0.4.1-alpine
  

  The reporter confirmed it worked and continued the setup. The maintainer also said the same tag is available on ghcr.io, even though the ghcr.io push briefly failed in CI with no clear reason. The failed push was to ghcr.io only; Docker Hub was not affected. If one registry refuses to resolve the tag on your host, try the same tag from the other registry.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Didn't work)

  Ran sudo docker run -t ghcr.io/sparfenyuk/mcp-proxy:v0.3.2-alpine --help on a Fedora CoreOS Docker host; Docker failed with "no matching manifest for linux/amd64 in the manifest list entries."

  Source: https://github.com/sparfenyuk/mcp-proxy/issues/24 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @sparfenyuk tried on GitHub (Worked)

  Maintainer suggested pulling the newer tag from Docker Hub with docker pull sparfenyuk/mcp-proxy:v0.4.1-alpine; the reporter confirmed it worked in a later comment.

  Source: https://github.com/sparfenyuk/mcp-proxy/issues/24#issuecomment-2644049989 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport