Skip to content

Allow "registry-mirrors" of gcr.io and other popular registries #41456

@myeyre

Description

@myeyre

Our servers inside corporate network can not connect to internet directly, and https proxy is not an option, so we use nexus to make registry proxies of popular registries like Docker Hub, gcr.io and etc.

Currently we can set "registry-mirrors" of Docker Hub through daemon.json, then we can pull images from proxy directly using same image name:

docker pull mysql:8

But for registries like gcr, we must address proxy url in pull command:

docker pull nexus_ip:registry_port/google_containers/pause:3.2

while pulling same image on internet:

docker pull k8s.gcr.io/google_containers/pause:3.2

It's a bit of inconvenience, cause some scripts or config files should be rewrite for intranet environment, while they where written on internet env.

How about allowing "registry-mirrors" of gcr.io and other popular registries?

Currently "registry-mirrors" setting:

{ "registry-mirrors": ["https://mirror.of.dockerhub"] }

We could change it to:

{ "registry-mirrors": { "https://hub.docker.com/": "https://mirror.of.dockerhub", "k8s.gcr.io": "mirror.of.gcr" } }

Is this possible? Could this be done?

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/distributionImage Distributionkind/enhancementEnhancements are not bugs or new features but can improve usability or performance.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions