This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong
FYI, I removed the block-proposed tag since ubuntu6 fixes this bug.
** Tags removed: block-proposed
--
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/1895967
Title:
Christian - thanks for your work on debugging this - can you please
remove the block-proposed tag if you are happy that 3.0.0~beta1-0ubuntu6
resolves this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
I uploaded 3.0.0~beta1-0ubuntu6 just now that should address this issue.
Thanks Christian for your debugging!
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: apparmor (Ubuntu)
Status: Confirmed => In Progress
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
Tested the change - works as expected, prepping an MP
--
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/1895967
Title:
Apparmor 3.0.0 does not load profiles in containers
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/apparmor/+git/apparmor/+merge/391134
--
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/1895967
That patch by Christian Bolz is already applied (which seems reasonable after
that much time),
but when merging 3.0 the old patch for bug 1824812 should have been dropped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
As refrence, it is a re-occurrence of
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1824812 , look
who filed that bug :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://gitlab.com/apparmor/apparmor/-/commit/61c27d8808f0589beb6a319cc04073e8bb32d860
--
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/1895967
Title:
Apparmor 3.0.0 does
And we are back with Christian Bolz :-)
commit 61c27d8808f0589beb6a319cc04073e8bb32d860
Author: Christian Boltz
Date: Fri Jun 21 19:22:15 2019 +0200
Fix and simplify setting SFS_MOUNTPOINT
The question is why isn't this in the apparmor 3.0 package in groovy-
proposed ?
--
You received
Isn't that "Not starting AppArmor in container" message just in:
/lib/apparmor/apparmor.systemd
-> /lib/apparmor/rc.apparmor.functions
-> function is_container_with_internal_policy()
That looks unchanged (except a comment) but it behaves differently:
root@testguest-apparmor-good:~# .
Still chasing this down
The apparmor.systemd file is unchanged from focal.
The change is in rc.apparmor.functions which is a dependency of
apparmor.systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
13 matches
Mail list logo
