Unable to use Custom Image Name

[kameshsampath]

I tried used custom image name with my mcp server e.g. ghcr.io/my-image, I see when IO connect to client e.g. Claude I see the following error

pulling docker images: pulling docker image ghcr.io/my-image: Error response from daemon: error from registry: denied

But I was able to do docker pull ghcr.io/my-image successfully. This is preventing me from testing the server locally before sending the PR. I also tried using imagename mcp/<image> and did task build with same result from the client.

CC: @designcode

[cmrigney]

Could you verify this is still an issue on the latest gateway? You can download it here and put the docker-mcp binary in ~/.docker/cli-plugins (on Mac). I was not able to repro on the current version.

[cmrigney]

Actually, I just saw there was a confirmed issue with the gateway, which we just fixed this week. If you update Docker Desktop to the latest (make sure modules are up to date as well), then it should be working now.

[jpicklyk]

I had to remove Claude desktop as the client and add back after the latest gateway update. Now my server that is referenced at ghcr.io works correctly.

[kameshsampath]

@cmrigney I see it works now. I see I can't do task build as it expects only mcp namespace. But I am still struck with the issue #50 thats preventing me to submit the server to the catalog.

cc: @ipedrazas