Expected behavior Expect when setting the dns and dns-search configurations, I should be able to pull from local registry without the FQDN. Actual behavior When I do pull without the FQDN, I get: $ docker pull <insecure registry>:5000/<org>/centos6.6-kitchen Using default tag: latest Pulling repos…

The --dns setting affects the dns for containers, but pull is done by the daemon itself, and changing the dns setting does not affect what the host sees, so this is expected behaviour. Docker will never interfere with the host /etc/resolv.conf settings, this would be a problem. We could potentially …

Hello @justincormack , That’s what I figured, that it’s a host level change. When I used docker-machine, the booted VM would pick up the correct search domain from the host machine. $ docker-machine ssh dev ... Boot2Docker version 1.11.0, build HEAD : 32ee7e9 - Wed Apr 13 20:06:49 UTC 2016 Docker v…

Hello, I think we have the same issue here at Ticketfly: our Docker registry is behind our VPN, with an internal FQDN my Mac can resolve the FQDN thanks to our internal DNS server docker-compose can’t resolve the FQDN, see below ~ docker-compose up pulling mysql (dev-artifactory.tfly-internal.c…

Same Error here ERROR: Service ‘wadev’ failed to build: Error while pulling image: Get https://index.docker.io/v1/repositories/library/ubuntu/images: dial tcp: lookup index.docker.io on 192.168.65.1:53: no such host

Same here {“errorDetail”:{“message”:“Error while pulling image: Get http://registry.mydomain.lan:5000/v1/repositories/ubuntu/images: dial tcp: lookup registry.mydomain.lan on 192.168.65.1:53: no such host”},“error”:“Error while pulling image: Get http://registry.mydomain.lan:5000/v1/repositories/ub…

This issue is quiet annoying. Not reflecting correct DNS configuration from host to xhyve is preventing workflow in any kind of environment with often switches between networks. May I suggest service restarts to mirror resolv.conf on the vm?

As an alternative solution - if you use the legacy Docker Tools OR a boot2docker VirtualBox Docker machine configuration, VirtualBox offers a solution to this problem. Just power down the VM then run: VBoxManage modifyvm "<VM-name>" --natdnshostresolver1 on DNS resolution worked perfectly for me …

Thanks so much, that workaround did work for me too. Can finally drop the VirtualBox VM :smiley: The only annoying part, as the workaround mentions, one has to do this each time the machine restarts :cry: Edit: looks like it’s not a workable solution… Docker for Mac keeps resetting the host resolu…

Custom /etc/resolv.conf in Docker for Mac, or using --dns-domain

Docker Desktop

irachex (Huayi Zhang) June 6, 2016, 9:29am 8

Same here.
Workaround mentioned here works for me.

Topic		Replies	Views
Docker pull not using correct DNS server when private registry on VPN Docker Desktop macos	31	58062	January 20, 2017
Docker pull ignores /etc/hosts file Docker Desktop dns , insecure-registry	2	4871	July 15, 2016
Docker for mac cannot resolved domain from /etc/hosts Docker Desktop dns , docker , build	3	4798	August 18, 2016
Unable to configure local network DNS Docker Desktop	0	866	April 18, 2016
Docker for Mac & Host VPN DNS don't cooperate Docker Desktop macos	10	16577	November 2, 2016

Custom /etc/resolv.conf in Docker for Mac, or using --dns-domain

Related topics