[Bug 1905493] Re: cloud-init status --wait hangs indefinitely in a nested lxd container

[Dan Streetman]

I wonder if this is actually a problem with the specific apparmor
profile that's created by lxd, maybe it doesn't provide enough
permissions to allow the container's lxd to correctly pass the apparmor
profile down to the nested container. Similar to how lxd locks down
containers a bit too tight by default and requires enabling
'security.nesting' just to be able to create a nested container.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1905493

Title:
  cloud-init status --wait hangs indefinitely in a nested lxd container

Status in AppArmor:
  New
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/apparmor/+bug/1905493/+subscriptions