https://bugzilla.redhat.com/show_bug.cgi?id=1128208
--- Comment #17 from Bill C. Riemers <briemers(a)redhat.com> ---
I've been having a bit of trouble with this workaround. Everytime I reboot I
have to manually run the following commands:
sudo systemctl restart dnsmasq
sudo systemctl restart docker
sudo systemctl restart iptables
Everything starts up running, but it seems not consistently in the right
sequence. Usually my iptables rules are not loaded at all, and sometimes my
docker containers do not have access to dnsmasq. Today I had the fun time
that docker seemed to start before all the networking so none of my containers
could even ping ipv4 addresses.
Restarting all the services manually seems to work, but this seems to indicate
that services are starting in random sequences in relations to docker.
Bill
--
You are receiving this mail because:
You are on the CC list for the bug.