-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Revert apparmor_parser regression
#8086
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert apparmor_parser regression
#8086
Conversation
This reverts commit 1acca8b. As stated in the Godoc, this function is intended to check for presence of `apparmor_parser`. Changing this regressed the public API of containerd, and directly contradicts the way that this function is consumed inside of containerd itself: * https://github.com/containerd/containerd/blob/fdfdc9bfc0f865a43c88171110615d1510fad3bc/pkg/apparmor/apparmor.go#L20 * https://github.com/containerd/containerd/blob/fdfdc9bfc0f865a43c88171110615d1510fad3bc/pkg/cri/sbserver/helpers_linux.go#L85 * https://github.com/containerd/containerd/blob/fdfdc9bfc0f865a43c88171110615d1510fad3bc/pkg/cri/server/helpers_linux.go#L144 This has lead to a number of painful regressions and attempted fixes in Moby: * moby/moby#44900 * moby/moby#44902 * moby/moby#44970 While reverting this late into the life of 1.6 and at the start of the life of 1.7 is likely painful, I think this is ultimately the best path to take, as containerd is subject to the same failure to start containers with an AppArmor kernel when `apparmor_parser` is missing as Moby. Signed-off-by: Bjorn Neergaard <[email protected]>
|
Hi @neersighted. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
876cd2f to
c58b2ae
Compare
Signed-off-by: Bjorn Neergaard <[email protected]>
c58b2ae to
d33a43c
Compare
thaJeztah
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
estesp
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
/ok-to-test |
dims
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This commit updates balena-containerd to a new version in which we cherry-picked the change from here: containerd/containerd#8086 This change avoids enabling AppArmor if the `/sbin/apparmor_parser` binary is not found in the system. Signed-off-by: Leandro Motta Barros <[email protected]> Change-type: patch
This reverts commit 1acca8b.
As stated in the Godoc, this function is intended to check for presence of
apparmor_parser. Changing this regressed the public API of containerd, and directly contradicts the way that this function is consumed inside of containerd itself:containerd/pkg/apparmor/apparmor.go
Line 20 in fdfdc9b
containerd/pkg/cri/sbserver/helpers_linux.go
Line 85 in fdfdc9b
containerd/pkg/cri/server/helpers_linux.go
Line 144 in fdfdc9b
This has lead to a number of painful regressions and attempted fixes in Moby:
While reverting this late into the life of 1.6 and at the start of the life of 1.7 is likely painful, I think this is ultimately the best path to take, as containerd is subject to the same failure to start containers with an AppArmor kernel when
apparmor_parseris missing as Moby.