Docker Community Forums

Share and learn in the Docker community.

Problems using local registry mirror in a closed network


(Shjensen) #1

Hi, I’ve followed the instructions on how to set up a local registry mirror and connect to it as given here: https://github.com/docker/docker/blob/master/docs/sources/articles/registry_mirror.md

Our Docker daemons are running on vm’s that have no Internet connection and thus rely on being able to pull images from the local registry mirror. However, it seems that even though the Docker daemon is configured to use the local registry, it still tries to contact index.docker.io initially.
Doing an i.e. docker pull java:8-jre results in the following error:

FATA[0000] Get https://index.docker.io/v1/repositories/library/java/images: dial tcp 162.242.195.84:443: connection refused

It was my hope that when using a registry mirror this would be the only service the Docker daemon would have to access in order to pull images. If the Docker daemon still needs to query the index.docker.io before pulling an image from registry mirror, it would mean that it’s not possible to do so from a machine which has no Internet connection.

Am I missing something here in terms of configuration, or how do I achieve the setup that I need?

Regards,
Simon