Thanks for this Markos. Rolling back has worked for me and I'll attempt updating the firewalld config next time I update. On Tue, Aug 28, 2018 at 12:15 PM Markos Chandras wrote:

On 28/08/18 11:17, Michael Aquilina wrote:

...

Hi guys,

It seems like any kind of network connection on docker fails to work ever since a recent upgrade.

Is anyone else having this issue?

I'm not entirely sure what changed but I'm having trouble debugging it since I don't understand at which point the failure is occurring or even how to investigate that.

This probably https://bugzilla.opensuse.org/show_bug.cgi?id=1105899

Current workaround is probably to switch the backend back to iptables. I have opened an SR to make iptables once again the default one so whoever wants to try nftables instead, they must explicitly switch it on in the /etc/firewalld/firewalld.conf file

-- markos

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- Michael Aquilina -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op dinsdag 28 augustus 2018 16:31:01 CEST schreef Michael Aquilina:

Can confirm that changing `FirewallBackend` from `'nftables` to `iptables` works as a temporary measure :) On Tue, Aug 28, 2018 at 1:42 PM Michael Aquilina

wrote:

...

Thanks for this Markos.

Rolling back has worked for me and I'll attempt updating the firewalld config next time I update.

On Tue, Aug 28, 2018 at 12:15 PM Markos Chandras wrote:

...

On 28/08/18 11:17, Michael Aquilina wrote:

...

Hi guys,

It seems like any kind of network connection on docker fails to work ever since a recent upgrade.

Is anyone else having this issue?

I'm not entirely sure what changed but I'm having trouble debugging it since I don't understand at which point the failure is occurring or even how to investigate that.

This probably https://bugzilla.opensuse.org/show_bug.cgi?id=1105899

Current workaround is probably to switch the backend back to iptables. I have opened an SR to make iptables once again the default one so whoever wants to try nftables instead, they must explicitly switch it on in the /etc/firewalld/firewalld.conf file

-- markos

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- Michael Aquilina This also solves/works around my issue of collabora/code not working with kernel 4.18

-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 29/08/18 06:04, Michal Kubecek wrote:

I'm slightly worried that everybody's response was like "it works again, problem solved" and so far nobody made an attempt to find out what was wrong. It kind of confirms Markos' concern from bsc#1105899 comment 17.

Michal Kubecek

For this particular problem, a bug is already filed upstream so we know what's wrong with it. But yeah, overall, it would be nice if people can switch back to nftables if possible to give it a go because we will have to switch back to it being the default option at some point. We can't switch back and forth every time we hit an nftables problem :) -- markos SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org