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
I tried restart snapd.apparmor. service and apparmor.service but it does not help. /pastebin. ubuntu. com/p/YbgG6PTBd g/
https:/
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' rw,hidepid= 2 /proc
# lxc exec finer-burro -- mount -o remount,