Unable to use Custom Image Name
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 555
- Forks
- 1.5k
- Avg merge
- 9h 53m
- Merged PRs (30d)
- 1
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the client connection with the custom image name ghcr.io/my-image and compare it with a direct docker pull, including the mcp/ variant and task build. Trace the image-pulling entry point in the Go project; done means the client can pull and use the custom image without the registry denied error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100