--- Comment #14 from Marek Goldmann <mgoldman(a)redhat.com> ---
(In reply to Josh Poimboeuf from comment #13)
Sorry, I misunderstood. It should be ok for docker to leave the
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
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.
OK, this makes sense.
The debug trace you posted seemed to show that docker0 already
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.
I wouldn't assume this, since the rules are executed no matter if the docker0
interface is started up or not:
This bridge was created by running the systemd service, no other tool created
You are receiving this mail because:
You are on the CC list for the bug.