https://bugzilla.redhat.com/show_bug.cgi?id=1033606
--- Comment #13 from Josh Poimboeuf <jpoim...@redhat.com> --- > Josh, above are devices. These cannot be listed with the "systemctl > list-unit-files" command. I think the real issue is that docker leaves the > docker0 interface running, even after we stop the service. WDYT? Sorry, I misunderstood. It should be ok for docker to leave the docker0 bridge device after it exits. In fact it's probably necessary so that already running containers won't lose their network if the docker daemon has to restart. When docker starts up, it checks for the existence of docker0. If it doesn't exist then it creates it and sets up the iptables rules appropriately. So future starts of docker will re-use the same bridge device, which should work fine. The debug trace you posted seemed to show that docker0 already existed. So what I'm still confused about is how is the the docker0 device getting created to start with? It looks like somebody created docker0 without setting up its needed iptables rules. -- 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
