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

2019-06-11 Thread Jonathan Dowland
severity 865975 critical thanks My report just got merged into this one as a duplicate, so sorry for being late to the party… On Tue, Nov 27, 2018 at 12:42:28PM +1100, Dmitry Smirnov wrote: I'm lowering severity back to "important". You are not wrong that Docker is hostile to other

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

2018-11-27 Thread Marvin Renich
[I'm subscribed to this bug, you don't need to include me in TO or CC.] * Dmitry Smirnov [181126 20:45]: > This bug is basically a duplicate of #903635. Not really. Bug #903635 is about not obeying a documented command line option. This bug is about incorrectly modifying iptables when it is

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

2018-11-26 Thread Dmitry Smirnov
This bug is basically a duplicate of #903635. On Tuesday, 27 November 2018 9:00:20 AM AEDT Marvin Renich wrote: > HUH??? Since when is it okay for software that is not advertised as > firewall software to modify the sysadmin's implicit or explicit iptables > setup for IP packets completely

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

2018-11-26 Thread Marvin Renich
Control: severity -1 critical * Alban Browaeys [171022 00:01]: > The FORWARD chain policy is set to DROP by docker since 1.13. HUH??? Since when is it okay for software that is not advertised as firewall software to modify the sysadmin's implicit or explicit iptables setup for IP packets

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

2018-06-07 Thread Dmitry Smirnov
I'm lowering severity of this bug since it is not clear how to reproduce the problem and because networking is not broken for everyone... signature.asc Description: This is a digitally signed message part.