I believe this was traced to people using snapd inside privileged LXD
containers, thus mixing kernel sandbox configuration from the host with
the guest. The guest was using different version of snapd than the host
but was confined by the host's apparmor profile for snap-conifine. Over
time snap-conifne started to use a new directory for locks and stopped
working.
This cannot be fixed as snapd cannot operate inside privileged
containers without apparmor stacking.b
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Won't Fix
** Changed in: snapd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734845
Title:
hook (core) configure → exit status 1 cannot create lock directory
/run/snapd/lock → Permission denied
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1734845/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
