i think either -L or -S "made everything work". Note that there is no iptables installs in the lxd container, and we install iptables on the fly.
nftables are not installed either, because that's not in main. So when lxd container started, nothing did "restore" of any default chains I don't think. But also have no idea if any are needed, or if I can tune any debugging in the kernel to notice if iptables are poked in some odd ways inside the network namespace that we are in. Also note all the extra setup that launchpad-buildd does: https://git.launchpad.net/launchpad-buildd/tree/lpbuildd/target/lxd.py in terms of creating lxd profile, and doing stuff to the bridge with iptables. I wonder if I must always use legacy iptables, if that's what used on the host to configure the bridge of the lxd container one is in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
