https://bugzilla.redhat.com/show_bug.cgi?id=1184710
Bug ID: 1184710
Summary: dnsmasq needs to be restarted after reboot for dns to
work in a Docker container
Product: Fedora
Version: 21
Component: docker-io
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected]
External Bug ID: Red Hat Bugzilla 1128208
External Bug ID: Red Hat Bugzilla 1128208
Description of problem:
Docker replies on dnsmasq to have 'listen-address' set to the docker bridge,
and have bind-interfaces option turned on. However in this configuration
dnsmasq has to start after docker in order for DNS to work in a docker
container.
Version-Release number of selected component (if applicable):
docker-io 1.4.0
dnsmasq 2.72
How reproducible:
Reboot the system with docker, and dnsmasq enabled.
Steps to Reproduce:
1. Ensure docker is using the default dns option of 172.17.42.1
2. Use the attached dnsmasq.conf
3. Reboot the system
4. Launch a docker container:
`docker run -i -t centos /usr/bin/ping www.redhat.com`
Actual results:
Cannot resolve hostname
Expected results:
Response from 'akamai' or similar
Additional info:
See related issue #1128208
I tried added a systemd 'After' for dnsmasq on docker.service, but it doesn't
seem to be honoured by systemd.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
golang mailing list
[email protected]
https://lists.fedoraproject.org/mailman/listinfo/golang
