Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2127244
Title:
Nested LXD is broken with snapd 2.71+ubuntu22.04
Status in snapd:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
The new snapd deb in -proposed for Ubuntu 22.04 breaks running LXD
nested in a LXD container resulting in
root@j0:~# sudo snap install --channel=5.21/stable lxd
error: cannot perform the following tasks:
- Start snap "lxd" (35624) services (systemctl command [start
snap.lxd.activate.service] failed with exit status 1: stderr:
Job for snap.lxd.activate.service failed because the control process exited
with error code.
See "systemctl status snap.lxd.activate.service" and "journalctl -xeu
snap.lxd.activate.service" for details.)
Can be reproduced with
$ multipass launch noble --name test -d 10G
test$ snap install --channel=5.21/stable lxd
test$ sudo lxd init --auto
test$ lxc launch ubuntu:j j0 -c security.nesting=true
test$ lxc shell j0
j0$ sudo snap remove --purge lxd
j0$ cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted
main multiverse universe
EOF
j0$ apt update ; apt upgrade
j0$ snap install --channel=5.21/stable lxd
We only see this on noble with kernel 6.14 when running Ubuntu 22.04
containers. Running the host with jammy and older kernels does not
show the same problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2127244/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
