lxd hanging at Waiting for network to be ready...

Status changed to 'Confirmed' because the bug affects multiple users.

This also affects me on Jammy.

I experienced the same bug until I realized the problem was caused by ufw, which was keeping the lxd container from obtaining an ipv4 address. Did you setup ufw? Does the problem persist if you disable it?

/var/log/syslog has:

Oct 7 15:42:33 laptop kernel: [21375.839338] [UFW BLOCK] IN=lxdbr0 OUT= PHYSIN=vethdfc21f4f MAC=00:16:3e:38:26:a2:00:16:3e:4d:c5:95:86:dd SRC=fe80:0000:0000:0000:0216:3eff:fe4d:c595 DST=fe80:0000:0000:0000:0216:3eff:fe38:26a2 LEN=78 TC=0 HOPLIMIT=64 FLOWLBL=740385 PROTO=UDP SPT=32931 DPT=53 LEN=38

So DNS is blocked.

$ sudo ufw status verbose
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), deny (routed)
New profiles: skip

Disabling ufw is a usable workaround.

BUT disabling ufw is not recommendable security-wise. snapcraft should come with the necessary ruleset for running behind ufw.

There is an NFT rule allowing routing:

        chain out.lxdbr0 {
                type filter hook output priority filter; policy accept;
                oifname "lxdbr0" tcp sport 53 accept
                oifname "lxdbr0" udp sport 53 accept
                oifname "lxdbr0" icmp type { destination-unreachable, time-exceeded, parameter-problem } accept
                oifname "lxdbr0" udp sport 67 accept
                oifname "lxdbr0" icmpv6 type { destination-unreachable, packet-too-big, time-exceeded, parameter-problem, echo-request, nd-router-advert, nd-neighbor-solicit, nd-neighbor-advert, mld2-listener-report } accept
                oifname "lxdbr0" udp sport 547 accept
        }

But that is irrelevant as iptables forbid it:

Chain FORWARD (policy DROP)

Why do we have this mixture of iptables and nft?

The problem only occurs if ufw firewall is active. The package should install firewall rules.