https://bugzilla.redhat.com/show_bug.cgi?id=1128208
--- Comment #1 from Lars Kellogg-Stedman <lars(a)redhat.com> ---
It is possible to update the docker options to work around the
problem. But of course the DNS servers obtained by DHCP, so it
would require restarting docker-io with new settings everytime a new
network connection is established...
You could just configure docker dns to point at the docker bridge
address (172.17.42.1), and then run a dnsmasq instance attached to
that bridge.
You can add the appropriate --dns option to /etc/sysconfig/docker.
With this in place, dnsmasq will take care of forwarding requests
appropriately, and you will not have to restart either docker or dnsmasq in the
event that your system resolver configuration changes.
Also, note that if docker tried to use 127.0.0.1 as a nameserver, it would fail
(because inside a docker container, 127.0.0.1 maps to the container, not to the
hsot).
--
You are receiving this mail because:
You are on the CC list for the bug.