Whitelisting Docker Hub Hosts for Firewalls and HTTP Proxy Servers

Organizations hosting a Nexus Repository Manager instance may have firewalls or HTTP Proxy Servers which must explicitly allow access to external hosts from internal networks.

Public registries such as the Docker Hub use multiple hosts and Content Delivery Networks (CDN) to serve content and scale requests.

In order for Nexus Repository Manager to have a Docker Hub proxy repository which works correctly, repository manager must be able to have full HTTP access to the following hosts:

https://auth.docker.io

https://registry-1.docker.io

https://index.docker.io/

https://dseasb33srnrn.cloudfront.net/

This list is subject to change at the whim of Docker Inc. and is not in control of Sonatype.

If your Docker Hub proxy repository is not working correctly, you can enable outbound HTTP request DEBUG level logging to examine the requests being made from repository manager to verify that outbound requests are reaching their intended endpoint.

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk