Looks like we are hit by a very similar issue (on amd64). Me and a colleague are having problems launching both ubuntu:22.04 and ubuntu:20.04 LXC containers since last week. Seems like someone else had asked about this on askubuntu.com too recently: https://askubuntu.com/questions/1484049/lxd-ubuntu-image-startup-issue-snap-lxd-activate-service-not-found. This response is by my colleague: https://askubuntu.com/a/1489496/148223. Also asked about on https://discourse.ubuntu.com/t/ubuntu-22-04-and-20-04-containers-stuck-in-system-is-booting-up-state/39470/4.
We are yet to find a way of reproducing it outside our own machines though. I tried setting up LXD on an internal server and there it works perfectly fine, so it's definitely not broken everywhere.
I'm on Ubuntu 22.04 with LXD 5.18-da72b8b.
Looks like we are hit by a very similar issue (on amd64). Me and a colleague are having problems launching both ubuntu:22.04 and ubuntu:20.04 LXC containers since last week. Seems like someone else had asked about this on askubuntu.com too recently: https:/ /askubuntu. com/questions/ 1484049/ lxd-ubuntu- image-startup- issue-snap- lxd-activate- service- not-found. This response is by my colleague: https:/ /askubuntu. com/a/1489496/ 148223. Also asked about on https:/ /discourse. ubuntu. com/t/ubuntu- 22-04-and- 20-04-container s-stuck- in-system- is-booting- up-state/ 39470/4.
We are yet to find a way of reproducing it outside our own machines though. I tried setting up LXD on an internal server and there it works perfectly fine, so it's definitely not broken everywhere.
I'm on Ubuntu 22.04 with LXD 5.18-da72b8b.