-
Notifications
You must be signed in to change notification settings - Fork 41.3k
Description
What happened?
when I change /etc/docker/demon
{
"exec-opts":["native.cgroupdriver=systemd"]
}
I describe the error pod pod/kube-proxy-zq5dk
Events:
Type Reason Age From Message
Normal Scheduled default-scheduler Successfully assigned kube-system/kube-proxy-zq5dk to node01
Normal Pulling 58m kubelet, node01 Pulling image "registry.aliyuncs.com/google_containers/kube-proxy:v1.16.0"
Normal Pulled 58m kubelet, node01 Successfully pulled image "registry.aliyuncs.com/google_containers/kube-proxy:v1.16.0"
Normal Created 58m kubelet, node01 Created container kube-proxy
Normal Started 58m kubelet, node01 Started container kube-proxy
Warning FailedCreatePodSandBox 51m (x11 over 53m) kubelet, node01 Failed create pod sandbox: rpc error: code = Unknown desc = failed to create a sandbox for pod "kube-proxy-zq5dk": Error response from daemon: cgroup-parent for systemd cgroup should be a valid slice named as "xxx.slice"
Normal SandboxChanged 3m39s (x232 over 53m) kubelet, node01 Pod sandbox changed, it will be killed and re-created.
What did you expect to happen?
I want to why? what can I do?
How can we reproduce it (as minimally and precisely as possible)?
change /etc/docker/demon
Anything else we need to know?
No response
Kubernetes version
kubectl version 1.16
Cloud provider
non
OS version
centos7