I have not seen/triggered the kernel issue mentioned in here (identified by
jdstrand).
But on request I'll try it at least.
Testing on Disco with Host Having:
5.0.0-13-generic
# Create container and trigger the issue:
lxc launch ubuntu-daily:d d-testapparmor
# update the container to not have the bug in apparmor userspace
lxc exec d-testapparmor apt update
lxc exec d-testapparmor apt upgrade
# Check status of AA in the container
Harr, this is not using shiftfs - therefore I can't trigger the bug yet.
Trying to get shiftfs to be active, not loaded yet
sudo modprobe shiftfs
sudo systemctl restart snap.lxd.daemon
# but creating a container still is empty
lxc exec d-testapparmor -- grep shiftfs /proc/self/mountinfo
<nothing>
Yep the daemon think it is not available
$ lxc info | grep shiftfs
shiftfs: "false"
I tried on this for a while but even
$ sudo snap set lxd shiftfs.enable=true
Won't set it to true.
I'm not sure I can verify this one as I don't know what blocks me from using
shiftfs in the first place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824812
Title:
apparmor does not start in Disco LXD containers
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1824812/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
