Based on the discussion in this bug report I'm marking this as fix
released.
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Released
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Fix Released
--
You received this
This is now merged in 2.32. Please see https://forum.snapcraft.io/t
/confined-snaps-dont-work-on-live-images-due-to-apparmor-path-
mapping/3767/9 if you want to check it out for yourself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
On 2 March 2018 at 11:37, Jamie Strandboge wrote:
So long as snapd starts before preinstalled snaps then all is fine.
>
Given that "preinstalled" snaps are merely seeded, there's nothing to be
worried about here :-)
--
You received this bug notification because you are a member of Ubuntu
Touch
*sigh* my test case in
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1751667/comments/8
was flawed. With the PR, on a livecd the apparmor unit correctly doesn't
load the policy. snapd starts at some point, notices it is on an
overlay, adds the overlay snippet to /var/lib/snapd/apparmor/sn
The problem is that the apparmor systemd unit (and the script it calls)
exit if /rofs/etc/apparmor.d exists. This is correct in the general
case. What needs to happen is either snapd loads them itself or the
apparmor init scripts instead load just the snap-confine profiles.
** Also affects: apparm
5 matches
Mail list logo
