containerd seems to have similar issues from Kubernetes... (I need to check if a bug exists for that as well)
kubelet.go:2049] [failed to "KillContainer" for "ceph-exporter" with KillContainerError: "rpc error: code = Unknown desc = failed to kill container \"373f6f3fc02b903a49b6d5e330366944e9cec71b697047807a2d1aa9a3362f97\": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown", failed to "KillPodSandbox" for "5d1942f2-81f0-4f8c-a970-e5b81a2869f7" with KillPodSandboxError: "rpc error: code = Unknown desc = failed to stop container \"373f6f3fc02b903a49b6d5e330366944e9cec71b697047807a2d1aa9a3362f97\": failed to kill container \"373f6f3fc02b903a49b6d5e330366944e9cec71b697047807a2d1aa9a3362f97\": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown"] (It seems like it might be a runc level issue, not just Docker) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063099 Title: Stopping container signal blocked by AppArmor on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/2063099/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
