Job for docker.service failed because start of the service was attempted too often. See "systemctl status docker.service" and "journalctl -xe" for details.

0 votes

Hi Guys,

I am trying to restart my docker engine. But it shows me the below error.

[root@localhost docker]# systemctl restart docker
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.

In jounalctl -xe comand, I found this below log.

-- Subject: Unit run-13263.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit run-13263.scope has finished starting up.
--
-- The start-up result is done.
May 27 12:46:42 localhost systemd[1]: Starting Kubernetes systemd probe.
-- Subject: Unit run-13263.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit run-13263.scope has begun starting up.
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.865671   13255 server.go:407] Version: v1.13.3
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.866194   13255 plugins.go:103] No cloud provider specif
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.885188   13255 certificate_store.go:130] Loading cert/k
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.896453   13255 server.go:666] --cgroups-per-qos enabled
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.896942   13255 container_manager_linux.go:248] containe
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.896963   13255 container_manager_linux.go:253] Creating
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.897106   13255 container_manager_linux.go:272] Creating
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.897180   13255 state_mem.go:36] [cpumanager] initializi
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.897340   13255 state_mem.go:84] [cpumanager] updated de
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.897360   13255 state_mem.go:92] [cpumanager] updated cp
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.897451   13255 kubelet.go:281] Adding pod path: /etc/ku
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.897494   13255 kubelet.go:306] Watching apiserver
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.904324   13255 client.go:75] Connecting to docker on un
May 27 12:46:42 localhost kubelet[13255]: I0527 12:46:42.904359   13255 client.go:104] Start docker client with
May 27 12:46:42 localhost kubelet[13255]: E0527 12:46:42.904541   13255 kube_docker_client.go:91] failed to retr
May 27 12:46:42 localhost kubelet[13255]: W0527 12:46:42.904571   13255 kube_docker_client.go:92] Using empty ve
May 27 12:46:42 localhost kubelet[13255]: F0527 12:46:42.904819   13255 server.go:261] failed to run Kubelet: fa
May 27 12:46:42 localhost systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
May 27 12:46:42 localhost systemd[1]: Unit kubelet.service entered failed state.
May 27 12:46:42 localhost systemd[1]: kubelet.service failed.
May 27 in Docker by akhtar
• 14,590 points
151 views

1 answer to this question.

0 votes

Hi@akhtar,

In your log, it shows that kubelet is not able to start its service and conflicts with your docker service. So I suggest you to remove your kubelet service.

$ yum remove kubelet.

After that you can start your docker service.

$ systemctl restart docker.

Hope this will help.

answered May 27 by MD
• 32,730 points

Related Questions In Docker

0 votes
2 answers

How can I inspect the file system of a failed `docker build

Failed command is a build that has ...READ MORE

answered Aug 6, 2018 in Docker by Nilesh
• 6,970 points
416 views
0 votes
2 answers
0 votes
1 answer
0 votes
1 answer
0 votes
1 answer

Deploy Docker Containers from Docker Cloud

To solve this problem, I followed advice ...READ MORE

answered Sep 3, 2018 in AWS by Priyaj
• 57,530 points
604 views
0 votes
1 answer

Job for docker.service failed because the control process exited with error code.

Hi@akhtar, Before starting your docker service check if ...READ MORE

answered Apr 14 in Docker by MD
• 32,730 points
590 views