Tom Parrott
Tom Parrott
@boltmark any news on this one?
For now the workaround is to do `lxc config set security.nesting=true` and restart container.
Reopens for privilege use case.
Have asked CPC about being able to apply a similar fix as https://github.com/canonical/lxd-imagebuilder/commit/c928d22574893208fd9ddbdb8c7dcf7e3899c19d to `ubuntu:` images. https://chat.canonical.com/canonical/pl/dygqosfbp3gy3x7hcs5ssergoy
@mihalicyn does this fix rely on the apparmor parser version in core24?
thanks @mihalicyn I've added the vendored apparmor parser and your fixes as cherry-picks to latest/stable now.
We are rolling out fixes to 5.21/stable for this now (`snap refresh lxd --channel=5.21/stable --cohort="+" ` will get it by bypassing progressive rollout).
@mihalicyn please can you verify that Oracular is working on Jammy host with 5.0/edge channel, if so then we can close this as the fix will be included in LXD...
LXD 5.0.4 now supports launching Oracular containers on a cgroupv2 enabled host https://discourse.ubuntu.com/t/lxd-5-0-4-lts-has-been-released/49681
@MggMuggins @markylaing are there any uses of an identity's projects list when not restricted?