Hi Ian,
If snap isn't supported/working in privileged containers that is a constraint
that is ok.
But while it is ok to "not work" since it is default installed in all images it
should at least not block all other activity in there (which blocking the full
boot is).
Could I ask for making snapd.seeded (or other components if that makes
more sense) to detect the situation and leave the system alone then?
That is exiting with "sorry I can't" or even better having a condition
that doesn't even try to start the service in that case.
Setting back to new to reconsider this request.
P.S. if anyone points me to an image with the change of 11058 that you
referred to I'm willing to test it for you in regard to this issue here.
** Changed in: snapd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952084
Title:
snapd.seeded.service never finishes on s390x when privileged or nested
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1952084/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
