-
Notifications
You must be signed in to change notification settings - Fork 79
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
disable cri-containerd.apparmor.d on ubuntu 24.04 #5354
disable cri-containerd.apparmor.d on ubuntu 24.04 #5354
Conversation
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5354-7c51e6b-containerd-1.6.33-k8s-ctrd-2024-08-22T22:16:47Z |
… and daily test cases also fix function name from 2024 to 2404
if is_ubuntu_2404 ; then | ||
# we need to disable apparmor on ubuntu 24.04 to allow pods to be deleted | ||
sed -i 's/disable_apparmor = false/disable_apparmor = true/' /etc/containerd/config.toml | ||
fi |
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.
I do not LIKE this solution
I think there is probably a better solution
I will keep looking for a better solution
This allows installations to complete in my testing
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5354-6e9e8d5-containerd-1.6.33-k8s-ctrd-2024-08-23T01:15:16Z |
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5354-e2cb549-containerd-1.6.33-k8s-ctrd-2024-08-23T01:31:43Z |
What this PR does / why we need it:
Before this, pod deletions failed with errors like:
This was accompanied by dmesg logs like
Turning off
cri-containerd.apparmor.d
entirely is a very blunt solution to this problem.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Steps to reproduce
Does this PR introduce a user-facing change?
Does this PR require documentation?