I tried restart snapd.apparmor.service and apparmor.service but it does not help. https://pastebin.ubuntu.com/p/YbgG6PTBdg/
I remembered when I created the container, the aa-status does show that lxd processes are in enforced mode. May be the issue only manifests after I rebooted the physical machine. Actually, I noticed the process disappeared from aa-status when I was trying to debug the mount with hidepid=2 inside the container. The steps I was performing at the time were # lxc exec finer-burro -- mount -v | grep '^proc' # lxc exec finer-burro -- mount -o remount,rw,hidepid=2 /proc -- 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/2006528 Title: LXD processes are not enforced in Ubuntu 20.04 HWE kernel Status in apparmor package in Ubuntu: New Bug description: In Ubuntu 20.04 server with HWE kernel (5.15.0-58-generic) and LXD 5.0.2, container processes are not in enforced mode as identified by aa-status Below are the output of aa-status in this environment. https://pastebin.ubuntu.com/p/kT3bHSS6w7/ The problem does not occur in Ubuntu 18.04 (https://pastebin.ubuntu.com/p/j4WcqWZRjH/) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2006528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
