I just started using the Docker for Mac beta, but immediately ran into an issue pulling from my company’s private registry which is hosted inside our VPN. It seems the docker daemon is trying to use Google’s DNS servers instead of the DNS servers set by the VPN. Expected behavior Docker pull should…

As far as I know, the bug tracker is not public so you won’t be able to follow on updates. However, if the issue is fixed you should see the issue number in the release notes.

I am facing the same problem with Version 1.11.1-beta14 (build: 8670). When I hop on VPN i get this ➜ ~ docker pull redis Using default tag: latest Pulling repository docker.io/library/redis Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/redis/images. Y…

Fingers crossed #3124 gets into the next release candidate, this causes me real pain when working from home

Facing the same issue with Docker version 1.12.0-rc2, build 906eacd, experimental, encountered via https://forums.docker.com/t/docker-pull-timeout/15015: $ docker pull hello-world Using default tag: latest Pulling repository docker.io/library/hello-world Network timed out while trying to connect t…

When using Docker Toolbox, its possible to configure the Virtualbox VM to use the host’s resolver. This gets around all of these problems. Any thing the Mac host can resolve, including /etc/hosts entries and domain specific DNS settings in /etc/resolver are automatically picked up, even when changed…

DNS resolution seems to have been fixed. With the current version 1.12.0-rc4-beta20 (build: 10404), I no longer have to apply any workarounds inside the moby VM to push/pull from our internal registry in our VPN.

Nope, doesn’t work for me, I still get an “i/o timeout” trying to login to our internal private registry using the latest “Docker for MAC” Beta - Version 1.12.0-rc4-beta20 (build: 10404) … it still is trying the wrong (external fallback) IP to communicate via https

This is not working for me either. I also tried the suggestions above up updating the resolve.conf within Apline and I still get the error “no route to host” when trying to pull images from my companies internal repository.

and just for reference, still not working in Version 1.12.0-beta21 (build: 11019), and even if I edit host and resolve.conf in the container it doesn’t really work it seems… the login works, but the pull/push e.g. times out

Docker pull not using correct DNS server when private registry on VPN

Docker Desktop

ibmrob (Ibmrob) July 22, 2016, 4:25pm 20

Not working for me either in 1.12.0-rc4-beta20 (build: 10404)

Topic		Replies	Views
Docker for Mac & Host VPN DNS don't cooperate Docker Desktop macos	10	16508	November 2, 2016
Docker does not pickup DNS information from Cisco AnyConnect Docker Desktop dns , docker , beta	5	12787	February 23, 2017
Custom /etc/resolv.conf in Docker for Mac, or using --dns-domain Docker Desktop	9	14174	August 9, 2016
Cannot pull from private repo on VPN Docker Desktop	2	2528	May 23, 2016
Auth.docker.io on 192.168.65.1:53: no such host Docker Desktop macos	35	126765	May 25, 2023

Docker pull not using correct DNS server when private registry on VPN

Related topics