Bug#865975: docker.io breaks (bridged) network for VMs

On Sun, Oct 22, 2017 at 02:00:58AM +0200, Alban Browaeys wrote: > or a config item in /etc/docker/daemon.json: > { > "iptables": false > } Seems like the docker.io package should ship this as a conffile then.

Bug#865975: docker.io breaks (bridged) network for VMs

Package: docker.io Followup-For: Bug #865975 The FORWARD chain policy is set to DROP by docker since 1.13. The verbose (-V) iptables output (which gives interfaces and packet counters) is: # iptables -L -v -n Chain INPUT (policy ACCEPT 281 packets, 14176 bytes) pkts bytes target prot opt

Bug#865975: docker.io breaks (bridged) network for VMs

Hi, docker is not configured in any special way, the only change to the config file was attached in the original report. Here are the relevant outputs of a full session after a fresh boot: after boot $ ip a s 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group

Bug#865975: docker.io breaks (bridged) network for VMs

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

Bug#865975: docker.io breaks (bridged) network for VMs

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