https://github.com/lxc/lxd/issues/3686#issuecomment-323570551
stgraber is really responsive to bug reports, that fix was quick. Do you think that it's worth adding the iptables[ipv6] dependency or should we just wait for v2.17?
is fine to wait the new release.
The fix was merged in https://github.com/gentoo/gentoo/pull/5621. I think we can close.
This does not solve the problem. I verified the commit from the pull request has made it into lxd-2.18 and lxd-2.19, however the same behaviour is observed if the kernel is not compiled with IPV6 support and ip6tables does not exist. lxd init fails and leaves a partial configuration. This should just skip the step for IPV6 and not terminate. Thank you, -Nik
Nikolay: I don't get a failure on my "-ipv6" system when I run "lxd init" as long as I answer "none" to the IPV6 bridge creation prompt. What did you answer at that prompt? auto? Is that the problem that you're, in fact reporting, that "auto" doesn't properly detect the absence of "ip6tables"?
Hello Virgil, I've looked further and the commit fixes missing ipv6 'filter' table, where the failure I get is for missing ipv6 'nat'. I've answered 'no' to IPV6 as I do not need it. See below: # lxd init Do you want to configure a new storage pool (yes/no) [default=yes]? no Would you like LXD to be available over the network (yes/no) [default=no]? Would you like stale cached images to be updated automatically (yes/no) [default=yes]? no Would you like to create a new network bridge (yes/no) [default=yes]? What should the new bridge be called [default=lxdbr0]? lxdbr2 What IPv4 address should be used (CIDR subnet notation, “auto” or “none”) [default=auto]? 192.168.124.1/24 Would you like LXD to NAT IPv4 traffic on your bridge? [default=yes]? What IPv6 address should be used (CIDR subnet notation, “auto” or “none”) [default=auto]? none error: Failed to list ipv6 rules for lxdbr2 (table nat) The setup I have is: iptables has ipv6 support, the kernel has the netfilter ipv6 NAT module compiled, however it is not loaded as not needed. net-firewall/iptables-1.4.21-r1::gentoo USE="ipv6 -conntrack -netlink -static-libs" zgrep -i "ipv6" /proc/config.gz | grep NAT CONFIG_NF_NAT_IPV6=m lxd is built with '-ipv6'. This setup causes the failure. You should be able to reproduce it. However the issue initially reported in commented #1 is for 'filter' and not 'nat'. So I believe this has to go mainline now? Thank you. -N
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7f091e8001253dfcd84e81d263d7db319b63aabf commit 7f091e8001253dfcd84e81d263d7db319b63aabf Author: Erik Mackdanz <stasibear@gentoo.org> AuthorDate: 2018-08-19 22:20:07 +0000 Commit: Erik Mackdanz <stasibear@gentoo.org> CommitDate: 2018-08-19 22:20:07 +0000 app-emulation/lxd: Bump to version 3.4 Add some dependencies used by upstream, fully build custom sqlite, move tools to IUSE. Closes: https://bugs.gentoo.org/show_bug.cgi?id=628346 Package-Manager: Portage-2.3.46, Repoman-2.3.10 app-emulation/lxd/Manifest | 1 + app-emulation/lxd/files/lxd.initd.1 | 47 ++++++++ app-emulation/lxd/lxd-3.4.ebuild | 232 ++++++++++++++++++++++++++++++++++++ app-emulation/lxd/metadata.xml | 5 +- 4 files changed, 284 insertions(+), 1 deletion(-)
