Source: docker.io Version: 18.06.1+dfsg1-2 Severity: normal Hi,
firewalld switched its default backend from iptables to nftables recently [1]. Unfortunately, this caused issues with libvirt and as reported in [2], also docker. I don't use docker myself, so I'm only relaying this information. The main problem seems to be, that currently there is no integration between docker and firewalld. Both manage firewall rules on their own. As soon as nftables(firewalld) and iptables(docker) are mixed, the result is a broken network setup. Please consider forwarding this issue upstream. Best is probably if docker upstream get's in touch with firewalld upstream to figure a solution. Regards, Michael [1] https://firewalld.org/2018/07/nftables-backend [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909574 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
