A few details/clarifications:
1) I can confirm that stopping the snapd.{service,socket} unblocks the
other services and allows the boot to finish (cloud-init finally reports
"done").
2) The problem happens when one launches an lxd container from a non-
amd64 architecture. For example, I have an s390x host machine and
cloud-init has successfully finished in it, but when I launch an ubuntu-
daily:impish/s390x container, I can reproduce the problem inside it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1944004/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
