如图所示：
在控制台里也是一样的
查看一下pod的详情
kubectl describe pod article-admin-5568cd9499-wqfp6 -n sob-service
全是英文，我也看不懂，查了一下新华字典，大概是权限有问题。
error killing pod: [failed to "KillContainer" for "container-55cm01" with KillContainerError: "rpc error: code = Unknown desc = Error response from daemon: cannot stop container: 564d931a42b6ac48de339fb9859d09e0e017327fbb9a2fa10316994ec7a9838d: Cannot kill container 564d931a42b6ac48de339fb9859d09e0e017327fbb9a2fa10316994ec7a9838d: unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown", failed to "KillPodSandbox" for "08b55312-605d-43e9-88e0-b2ea97cbcd2a" with KillPodSandboxError: "rpc error: code = Unknown desc = Error response from daemon: cannot stop container: 99842a2ff36101f31825e6b87ff7d7673a0e98d07cbb865b5c7f2a5a63a10156: Cannot kill container 99842a2ff36101f31825e6b87ff7d7673a0e98d07cbb865b5c7f2a5a63a10156: unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown"]
重点是这个：unable to signal init: permission denied
可能是AppArmor 影响 Docker/Kubernetes的
可以用sudo aa-status | grep docker查看一下
我都不查的，我直接关掉试试就知道是不是他的问题了
sudo systemctl stop apparmor
sudo systemctl disable apparmor
最后，当然关掉就好了。
