Build docker in centos.
At first everything went well, but after configuring the image, I restarted docker and got an error
Restarting docker reports the following error message:
Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details.
The start docker error message reads:
Job for docker.service failed because start of the service was attempted too often. See “systemctl status docker.service” and “journalctl -xe” for details.
To force a start use “systemctl reset-failed docker.service” followed by “systemctl start docker.service” again.
At first everything went well, but after configuring the image, I restarted docker and got an error
Restarting docker reports the following error message:
Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details.
The start docker error message reads:
Job for docker.service failed because start of the service was attempted too often. See “systemctl status docker.service” and “journalctl -xe” for details.
To force a start use “systemctl reset-failed docker.service” followed by “systemctl start docker.service” again.
Reason for the problem: daemon file suffix format causes reboot/boot failure
The solution is
1、Enter the docker directory: cd /etc/docker
2、Modify the suffix of daemon file: mv daemon.json daemon.conf
3, restart/start docker: systemctl start docker
image852×367 12.3 KB
Read More:
- Docker Open Error: Warning: docker.service changed on disk. Run ‘systemctl daemon-reload‘ to reload unit
- Docker service startup error: Job for docker.service failed because the control process exited with error code.
- [Solved] Job for docker.service failed because the control process exited with error
- [Solved] Rsync synchronization Error: @ERROR: Unknown module xxx
- [Solved] Postgres Start Error: Job for postgresql.service failed because the control process exited with error code.
- [Solved] “Failed to run kubelet“ err=“failed to run Kubelet: misconfiguration: kubelet cgroup driver: \“cgrou
- [Solved] Docker Error: Error response from daemon: driver failed programming external connectivity on endpoint
- How to Solve kubelet starts error (k8s Cluster Restarted)
- [Solved] K8s Initialize Error: failed with error: Get “http://localhost:10248/healthz“
- Docker Pull Error: certificate signed by unknown authority
- [Solved] Job for mysqld.service failed because the control process exited with error code.
- Mac Docker pull Error: Error response from daemon: Get https://xx.xx.xx.xx/v2/: Service Unavailable
- [Solved] Playbook Start Nginx Error: Unable to start service nginx: Job for nginx.service fd with error code
- [Solved] Docker Startup Error: panic: runtime error: invalid memory address or nil pointer dereference
- ubuntu docker dm_task_run failed error [How to Solve]
- [Solved] k8s kubeadmin init Error: http://localhost:10248/healthz‘ failed
- [Solved] harbor Error: because it doesn‘t contain any IP SANs
- [Solved] Docker Start Error: iptables failed: iptables –wait -t nat -A DOCKER -p tcp -d 0/0 –dport 10241
- Docker Build Error: Failed to get D-Bus connection: Operation not permitted [Solved]
- Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen is reported when docker port mapping or starting the container