Control: tags -1 +moreinfo On Mon, Jun 26, 2017 at 11:16:56AM +0200, Roland Kammerer wrote: > Package: docker.io > Version: 1.13.1~ds1-2 > Severity: critical > Tags: upstream > Justification: breaks unrelated software > > Dear Maintainer, > > * What led up to the situation? > Any docker command like "docker images" > > * What was the outcome of this action? > Network breaks for all libvirt VMs (i.e., they are not able to ping each > other, or public domains, and after a reboot they do not get an IP via > dhcp). The VMs are connected to a bridge (br0): > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > #allow-hotplug eth2 > #iface eth2 inet dhcp > # This is an autoconfigured IPv6 interface > #iface eth2 inet6 auto > > auto br0 > iface br0 inet dhcp > bridge_ports eth2 > # bridge_stp on > bridge_maxwait 0 > bridge_fd 0 > > I don't have any firewall/iptables rules on my machine. > > * What outcome did you expect instead? > That networking still works (as it did with older docker versions).
Which versions were working? > The situation can be fixed via "iptables -I FORWARD -i br0 -o br0 -j ACCEPT". > Before that I saw "Chain FORWARD (policy drop 3493 packests, 829K bytes)". > Therefore, I assume that docker messages with the chains. It would be useful if you could provide a step by step set of instructions on how to reproduce this. For example, what type of VMs does libvirt use? KVM? How is docker configured? What commands are ran exactly? Thanks, A.
signature.asc
Description: PGP signature
