© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Per discussion above:
- Closing the kernel tasks
- Raising priority on apparmor tasks to Critical (to match what kernel had)
- Assigning to jjohansen as the AppArmor maintainer
As we care about xenial, bionic and cosmic, we need point releases (or cherry-pick) for:
- AppArmor 2.10 (2.10.95 in xenial)
- AppArmor 2.12 (2.12 in bionic and cosmic)
John: Any ETA for those two point releases or pointer to a commit which we could SRU on its own?
For now our focus is obviously on getting this resolved in Ubuntu as soon as possible, since it's breaking a number of systemd services that are now (18.04) shipping with more confinement than in the past. The same issue is also currently preventing us from starting newer Fedora and Arch containers on Ubuntu.
Our standard response so far has been to tell users to turn off AppArmor for those containers, but it's obviously not an answer we like to give (I'm sure you'll agree).