[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-07-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: containerd-app (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-07-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: containerd-app (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-07-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: containerd-app (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-07-12 Thread Christopher J. Ruwe
Thank you for the clarification and thank you for your work! Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065423 Title: Update AppArmor template to allow confined runc to kill containers

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-07-10 Thread Lucas Kanashiro
It is fixed in the development release (when there is not specific series the default is development, in this case oracular). I am adding tasks for the supported series as well. The backport is a follow-up work. The server team will be doing that once we find the time. ** Also affects:

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-07-10 Thread Christopher J. Ruwe
I can see the updated package in oracular, but noble is still at 1.7.12-0ubuntu4. Well the package be updated in noble as well? Without, I wouldn't consider that fixed. Thanks for your efforts, cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-07-04 Thread Launchpad Bug Tracker
This bug was fixed in the package containerd-app - 1.7.19-0ubuntu1 --- containerd-app (1.7.19-0ubuntu1) oracular; urgency=medium * New upstream release. * d/t/basic-smoke: set proxy environment variables. -- Lucas Kanashiro Wed, 03 Jul 2024 18:52:03 -0300 ** Changed in:

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-06-19 Thread Christian Ehrhardt 
FYI: Uploaded by Lucas but atm stuck in proposed for networking issues in the test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065423 Title: Update AppArmor template to allow confined runc to

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-05-29 Thread Bryce Harrington
** Changed in: containerd-app (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065423 Title: Update AppArmor template to allow

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-05-22 Thread Athos Ribeiro
** Changed in: containerd-app (Ubuntu) Status: Confirmed => Triaged ** Tags added: server-todo ** Changed in: containerd-app (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-05-21 Thread Sebastian Podjasek
Apparently, that's the fate of early adopters... I've managed to "hand-craft" following apparmor profile and place it in: /etc/apparmor.d/cri-containerd.apparmor.d as a temporary solution for this problem. ** Attachment added: "Temporary working profile for apparmor"

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-05-21 Thread Christopher J. Ruwe
I am to some extend amazed considering so few users participate in this discussion. I'd expect every user of Kubernetes, using containerd and app_armor on an Ubuntu 24.04 to be affected. To get my clusters in a sustainable state, I deactivated app_armor for containerd as a stop-gap measure,

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-05-11 Thread Sebastian Podjasek
Forgot to paste link to PR related to issue above :/ https://github.com/containerd/containerd/pull/10129 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065423 Title: Update AppArmor template to

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-05-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: containerd-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065423

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

2024-05-11 Thread Dmitrii Kuptsov
Seeing this in Noble containerd 1.7.12-0ubuntu4 Seems to be https://github.com/containerd/containerd/pull/10123 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065423 Title: Update AppArmor template