You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
We are trying to confine Kubelet in an apparmor profile, we notcied that when kubelet tries to send a kill signal to a docker container that was under the docker-default apparmor profile. the signal is blocked.
Steps to reproduce the issue:
create apparmor profile for kubelet
schedule kubernetes crontab job with container using docker-default apprmor profile
Description
We are trying to confine Kubelet in an apparmor profile, we notcied that when kubelet tries to send a kill signal to a docker container that was under the docker-default apparmor profile. the signal is blocked.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
the signal should be accepted and not denied when kubelet is confined
Additional information you deem important (e.g. issue happens only occasionally):
we tried using kubernetes v1.19.11
Output of
docker version
:Additional environment details (AWS, VirtualBox, physical, etc.):
OS Ubuntu 18.04.5 LTS
The text was updated successfully, but these errors were encountered: