> If you can install the snapd snap then using 2.72 inside the container works around the issue and allows LXD to start (because its built with a newer version of Go that re-opens the stdout file handle that apparmor closes to /dev/null).
This doesn't quite work as a workaround in some cases. For example, jammy LXD container images seed the LXD snap and it fails to install as part of snapd.seeded.service and it blocks subsequent tasks so the boot doesn't complete. And if snapd.seeded.service is not complete, snapd doesn't accept an operation to install or refresh snapd. # snap install snapd error: too early for operation, device not yet seeded or device model not acknowledged # systemctl list-jobs JOB UNIT TYPE STATE 139 cloud-init.target start waiting 145 cloud-final.service start waiting 105 snapd.autoimport.service start waiting 140 cloud-config.service start waiting 1 graphical.target start waiting 2 multi-user.target start waiting 146 snapd.seeded.service start running 107 systemd-update-utmp-runlevel.service start waiting 8 jobs listed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127244 Title: Nested LXD is broken with snapd 2.71+ubuntu22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2127244/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
