After analysis, it is found that “kebernetes sets the CGroup driver to SYSTEMd by default, while the CGroup driver of docker service is cgroups”. There are two solutions. First, why is the service configuration file of docker the same as that of kubernetes? Second, modify the configuration file of kebernetes to cgroups. The first one is adopted here.
Modify the configuration file of docker service,/etc/docker/daemon.JSON, and add the following
"exec-opts": ["native.cgroupdriver=systemd"]
Restart dokcer service:
sudo systemctl daemon-reload
sudo systemctl restart docker
Restart kuberlet:
systemctl restart kubelet
Similar Posts:
- [Solved] http: server gave HTTP response to HTTPS client
- An error is reported when the docker command is executed in Jenkins
- [Solved] Docker Starup Error: Failed to start Docker Application Container Engine.
- Docker ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? [How to Solve]
- [Solved] kubeadm join 192.168.50.66:6443 –token 0109we.c3a3ofn0y0lmp0w9 –discovery-token-ca-cert-hash sha256:262f5eefdbeba51e6875cba5ed6e34061ad679f8a21f6e295d9fbd5ef05757e4
- Docker login harbor 403 Forbidden [How to Solve]
- Job for docker.service failed because the control process exited with error code. See “syste…
- [Solved] Failed to start Docker Application Container Engine.
- Error message after installing docker in CentOS 7
- Docker Error: Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details.