docker-mcp catalog must not be mandatory

[ThomasSteinbach]

The Problem

In my working environment I am restricted to pull images from some sources:

% docker pull mcp/context7
Using default tag: latest
Error response from daemon: requested access to the resource is denied - image access restricted: mcp/context7 blocked for organization xxxxxx

Thus the Docker mcp-gateway is not able to work with the default docker-mcp catalog, which pulls all images from mcp/*.

What I tried

• I made a copy of the current catalog and replaced all occurences of image: * by our Docker Hub Proxy (fictive example) image: docker.artifactory.net/*.
• I removed the docker-mcp Catalog from the configuration in ~/.docker/mcp/catalog.json and also removed the catalog in ~/.docker/mcp/catalogs/docker-mcp.yaml
• I restarted Docker Desktop

The problem persists as Docker Desktop restores the docker-mcp catalog.

Possible Solutions

• Allow an override or patch mechanism for the image URLs in a catalog
• Or allow to disable the docker-mcp catalog in favour of a self maintained catalog

[liuziyue]

Hi Thomas, thanks for opening the issue. The Docker team is currently working on a new feature that allows users to create private catalogs. I believe it would address your issue once it's released. We plan to pilot the feature to early adopters. If you're interested in trying it out firsthand, let us know and I will share more information as soon as the feature is available.

[ThomasSteinbach]

Cool. I'll track the public progress. Currently it's not urgent to me to be early adopter. But glad to hear that you have a solution in progress. Im curious how the Docker AI/MCP suite evolves.