FWIW I know what the snapd issue is, the issue is that snapd does not
and will not work in a nested LXD container, we need to add code to make
snapd.seeded.service die/exit gracefully in this situation.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
** Changed in: snapd
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1905493
Title:
cloud-init status --wait hangs indefinitely in a nested lxd container
Status in cloud-init:
Invalid
Status in snapd:
Confirmed
Status in dbus package in Ubuntu:
New
Status in systemd package in Ubuntu:
Invalid
Bug description:
When booting a nested lxd container inside another lxd container (just
a normal container, not a VM) (i.e. just L2), using cloud-init -status
--wait, the "." is just printed off infinitely and never returns.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1905493/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
