> This only works if the iptables modules aren't loaded in the 'host' system, correct?
I don't get your question. iptables-persistent doesn't work in containers in both cases: - When modules are not loaded. Since containers lack privileges to load them, this is not fixable. - When modules are loaded, because iptables-persistent calls modprobe which fails even when the required modules is already loaded. This is what this bug report is about. The modprobe error can be ignored, as iptables-save and friends will work fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820144 Title: iptables-persistent fails in containers due to modprobe being unavailable even though module could've been loaded outside of the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-persistent/+bug/1820144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
