Hello again, I now downloaded our previous debian-testing image, where the failure does not happen. This has the same kernel, docker, and libvirt version, and firewalld 0.6.3-1. Upgrading just firewalld to 0.6.3-3 introduces this regression. Presumably upstream now only tests with nftables, and the switch back to iptables caused this breakage?
> At boot, these errors already show up in the journal: This was a red herring. With 0.6.3-1, the same errors are also already in the firewalld journal, but replacing works: | # firewall-cmd --reload | success I tried to reproduce this on a minimal sid autopkgtest VM. libvirtd and docker are not related here, this fails with just: apt install firewalld firewall-cmd --reload # works reboot firewall-cmd --reload # fails Martin
