https://bugzilla.redhat.com/show_bug.cgi?id=1128208
--- Comment #10 from Lars Kellogg-Stedman <l...@redhat.com> ---
For what it's worth, I have dnsmasq listening on the docker bridge like this:
listen-address=172.17.42.1
bind-interfaces
And my docker daemon running like this:
/usr/bin/docker -d -H fd:// --selinux-enabled --dns=172.17.42.1
Which gets me /etc/resolv.conf in the container that looks like this:
nameserver 172.17.42.1
...and it all Just Works. You can fix the startup ordering issue by:
- Enabling the docker *service* unit (rather than the *socket*):
system enable docker
- Giving your dnsmasq service a Before= dependency on the docker service.
There are various ways of doing that; you could create
/etc/systemd/system/dnsmasq.service.d/docker.conf with the contents:
[Unit]
After=docker.service
Requires=docker.service
If you have docker listening on 172.17.42.1 and it's not working, it's possible
you may need to tweak iptables to permit access.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
golang mailing list
golang@lists.fedoraproject.org
https://lists.fedoraproject.org/mailman/listinfo/golang
