On Thu, Oct 06, 2016 at 02:02:09PM -0500, Dan Williams wrote:
On Thu, 2016-10-06 at 12:39 -0600, Nathanael D. Noblet wrote:
On Thu, 2016-10-06 at 14:28 -0400, Neil Horman wrote:
I rarely mess with docker, but I expect that the docker0 bridge has an ip address on it which may conflict with the one on libvirt bridge. That is to say, if they are on the same subnet, and the route for the docker0 bridge takes precidence, you will loose dhcp. Check the docker bridge ip and remove it if you see one, I expect that will restore your functionality
Unfortunately that isn't the issue as the docker bridge is 172... and bridge0 is 192.168... so they don't conflict. Also docker0 doesn't seem to have any devices (meaning it brctl show has no interfaces attached to it). Finally shutting down docker and removing docker0 doesn't restore connectivity, only a reboot does. Not even restarting NM fixes the issue.
Try running 'iptables-save' before you start docker, and then running 'iptables-save' after. Diff the results. Did docker remove anything?
+1, thats the next thing to look at. Both docker and libvirt use iptables to direct traffic in various ways. They may well be in conflict Neil
Dan _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org