Docker service job for docker service failed because the control process exited with error code

So I installed docker engine on RHEL 7 Now when I do a service docker start I get the following error: Job for docker.service failed because the control process exited with error code. See "

So I installed docker engine on RHEL 7

Now when I do a 

service docker start

I get the following error:

Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

and when I go to «systemctl status docker.service» and «journalctl -xe»
I get:

docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─docker.conf
   Active: failed (Result: exit-code) since Thu 2016-09-08 22:15:53 EDT; 10s ago
     Docs: https://docs.docker.com
  Process: 13504 ExecStart=/usr/bin/docker daemon -H fd:// --mtu 1400 --exec-opt native.cgroupdriver=systemd (code=exited, status=1/FAILURE)
 Main PID: 13504 (code=exited, status=1/FAILURE)

Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: Starting Docker Application Container Engine...
Sep 08 22:15:53 app-linux2.app-netapp.lab.com docker[13504]: time="2016-09-08T22:15:53.227074798-04:00" level=fatal msg="no sockets found via socket activation: make sure the service ...by systemd"
Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: Failed to start Docker Application Container Engine.
Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: Unit docker.service entered failed state.
Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: docker.service failed.

And

—

-- The start-up result is done.
Sep 08 22:10:01 app-linux2.app-netapp.lab.com CROND[12753]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Sep 08 22:10:01 app-linux2.app-netapp.lab.com systemd[1]: Starting Session 58 of user root.
-- Subject: Unit session-58.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-58.scope has begun starting up.
Sep 08 22:10:53 app-linux2.app-netapp.lab.com polkitd[766]: Registered Authentication Agent for unix-process:12878:2674931 (system bus name :1.173 [/usr/bin/pkttyagent --notify-fd 5 --fallback], ob
Sep 08 22:10:53 app-linux2.app-netapp.lab.com systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Sep 08 22:10:53 app-linux2.app-netapp.lab.com docker[12895]: time="2016-09-08T22:10:53.413304246-04:00" level=fatal msg="no sockets found via socket activation: make sure the service was started by
Sep 08 22:10:53 app-linux2.app-netapp.lab.com systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Sep 08 22:10:53 app-linux2.app-netapp.lab.com systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Sep 08 22:10:53 app-linux2.app-netapp.lab.com systemd[1]: Unit docker.service entered failed state.
Sep 08 22:10:53 app-linux2.app-netapp.lab.com systemd[1]: docker.service failed.
Sep 08 22:10:53 app-linux2.app-netapp.lab.com polkitd[766]: Unregistered Authentication Agent for unix-process:12878:2674931 (system bus name :1.173, object path /org/freedesktop/PolicyKit1/Authent
Sep 08 22:13:36 app-linux2.app-netapp.lab.com polkitd[766]: Registered Authentication Agent for unix-process:13214:2691210 (system bus name :1.174 [/usr/bin/pkttyagent --notify-fd 5 --fallback], ob
Sep 08 22:13:36 app-linux2.app-netapp.lab.com polkitd[766]: Unregistered Authentication Agent for unix-process:13214:2691210 (system bus name :1.174, object path /org/freedesktop/PolicyKit1/Authent
Sep 08 22:15:53 app-linux2.app-netapp.lab.com polkitd[766]: Registered Authentication Agent for unix-process:13489:2704913 (system bus name :1.175 [/usr/bin/pkttyagent --notify-fd 5 --fallback], ob
Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Sep 08 22:15:53 app-linux2.app-netapp.lab.com docker[13504]: time="2016-09-08T22:15:53.227074798-04:00" level=fatal msg="no sockets found via socket activation: make sure the service was started by
Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: Unit docker.service entered failed state.
Sep 08 22:15:53 app-linux2.app-netapp.lab.com systemd[1]: docker.service failed.
Sep 08 22:15:53 app-linux2.app-netapp.lab.com polkitd[766]: Unregistered Authentication Agent for unix-process:13489:2704913 (system bus name :1.175, object path /org/freedesktop/PolicyKit1/Authent
lines 3473-3523/3523 (END)

I tried to search solution for this
but could not find any.

Источник

@garyyang6

  • This is a bug report
  • This is a feature request
  • I searched existing issues before opening this one

Expected behavior

Docker should be started.

Actual behavior

Cannot start docker

At CentOS 7. Try to start docker. But, it is failed.

systemctl start docker
Job for docker.service failed because the control process exited with error code. See «systemctl status docker.service» and «journalctl -xe» for details.

Steps to reproduce the behavior

systemctl start docker

Output of docker version:
docker version
Client:
Version: 17.11.0-ce-rc3
API version: 1.34
Go version: go1.8.3
Git commit: 5b4af4f
Built: Wed Nov 8 03:04:32 2017
OS/Arch: linux/amd64
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

systemctl status docker.service
â—� docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Tue 2017-11-14 20:52:23 UTC; 6min ago
     Docs: https://docs.docker.com
  Process: 1661 ExecStart=/usr/bin/dockerd (code=exited, status=1/FAILURE)
 Main PID: 1661 (code=exited, status=1/FAILURE)

Nov 14 20:52:23 docker02.com systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Nov 14 20:52:23 docker02.com systemd[1]: Failed to start Docker Application Container Engine.
Nov 14 20:52:23 docker02..com systemd[1]: Unit docker.service entered failed state.
Nov 14 20:52:23 docker02..com systemd[1]: docker.service failed.
Nov 14 20:52:23 docker02.com systemd[1]: docker.service holdoff time over, scheduling restart.
Nov 14 20:52:23 docker02.com systemd[1]: start request repeated too quickly for docker.service
Nov 14 20:52:23 docker02.corp.com systemd[1]: Failed to start Docker Application Container Engine.
Nov 14 20:52:23 docker02.corp.com systemd[1]: Unit docker.service entered failed state.
Nov 14 20:52:23 docker02.corp.com systemd[1]: docker.service failed.

journalctl -xe
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tomcat.service has begun starting up.
Nov 14 20:59:36 sf-docker02.corp.wagerworks.com systemd[1833]: Failed at step EXEC spawning /opt/tomcat/bin/startup.sh: No such file
-- Subject: Process /opt/tomcat/bin/startup.sh could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The process /opt/tomcat/bin/startup.sh could not be executed and failed.
-- 
-- The error number returned by this process is 2.
Nov 14 20:59:36 docker02.com systemd[1]: tomcat.service: control process exited, code=exited status=203
Nov 14 20:59:36 docker02.corp.com systemd[1]: Failed to start Apache Tomcat Web Application Container.
-- Subject: Unit tomcat.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tomcat.service has failed.
-- 
-- The result is failed.
Nov 14 20:59:36 docker02.corp.com systemd[1]: Unit tomcat.service entered failed state.
Nov 14 20:59:36 docker02.corp.com systemd[1]: tomcat.service failed.
Nov 14 20:59:47 docker02.corp.com systemd[1]: tomcat.service holdoff time over, scheduling restart.
Nov 14 20:59:47 docker02.corp.com systemd[1]: Starting Apache Tomcat Web Application Container...
-- Subject: Unit tomcat.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tomcat.service has begun starting up.
Nov 14 20:59:47 docker02.corp.com systemd[1836]: Failed at step EXEC spawning /opt/tomcat/bin/startup.sh: No such file
-- Subject: Process /opt/tomcat/bin/startup.sh could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The process /opt/tomcat/bin/startup.sh could not be executed and failed.
-- 
-- The error number returned by this process is 2.
Nov 14 20:59:47 docker02.corp.com systemd[1]: tomcat.service: control process exited, code=exited status=203
Nov 14 20:59:47 docker02.corp.com systemd[1]: Failed to start Apache Tomcat Web Application Container.
-- Subject: Unit tomcat.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tomcat.service has failed.
-- 
-- The result is failed.
Nov 14 20:59:47 docker02.corp.com systemd[1]: Unit tomcat.service entered failed state.
Nov 14 20:59:47 docker02.corp.com systemd[1]: tomcat.service failed.

Output of docker info:

docker info
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Additional environment details (AWS, VirtualBox, physical, etc.)

lucasmafra, cnrmck, fanglingsu, tomcss, ronald-espinoza-mojix-com, bpsuntrup, orian, cafeduke, jerryliu306, grigored, and 19 more reacted with thumbs up emoji

@jiayoucoding

Hi, I’m having the same issue here, were you able to solve it?

lucasmafra, cnrmck, tomcss, bpsuntrup, mopsyd, ChristophSchranz, alittlebitcool, ankitshah009, scchess, io12, and 3 more reacted with thumbs up emoji

@davibusanello

Hello, I’am having same problem here in Manjaro Linux

NotBad4U, lucasmafra, dimensi0n, cnrmck, tomcss, mopsyd, jacksonpradolima, defunctl, gauthamzz, RicardoVeronica, and 4 more reacted with thumbs up emoji

@liaozd

+1 here, same on both ubuntu and CentOS, have to downgrade to docker version.

@markrcu

same issue here any solution?

@jeroenev

same, let me know if you find a solution, also using manjaro linux

@jeroenev

reverting back to the previous kernel version fixed it for me (only use LTS kernels, moved from 4.9 to 4.14, which seems to have caused the issue, moving back to 4.9 fixed it.)

@garyyang6

Remove /var/lib/docker (rm -rf /var/lib/docker). Restart Docker solved the problem.

teberl, timzaak, vineshvsv, yx1989, marco-lavagnino, fxrcode, nikgalushko, CaioPenhalver, agomezrominsait, yh8i9kb8n, and 67 more reacted with thumbs up emoji
DivyaJyotiDas, GoTheExtraMile, atsikham, CoskunSunali, euventura, zhang3550545, thomasks, lematt1991, esxi1979, tomersh, and 76 more reacted with thumbs down emoji
karimbeji, jiemin0049, prashant182, troymaclure, eelessam, Garey27, rbotarleanu, spalonytoster, xuyuan1, orian, and 7 more reacted with laugh emoji
karimbeji, jiemin0049, kid1412621, theerapan-TH, eelessam, chatchaw, Cheesedip, YvZheng, spalonytoster, xuyuan1, and 7 more reacted with hooray emoji
tomcss, cy94, zhaosr, stroykova, FabianLauer, Y-LyN-10, qwvLJV7C, ChandraLee, ju5tevg3niy, and Apologiz reacted with confused emoji
karimbeji, jiemin0049, kid1412621, eelessam, kosarinin, spalonytoster, roshnikasliwal, xuyuan1, fatemeakbari, tsimchev, and 4 more reacted with heart emoji

@santy92

garyyang6 — yes your right removing docker files solved the issues, but we lost the images which we installed before..do you have any other solutions to bring back the images or any other trick to solve the issue..

@ghost

+1 Same Issue mith Manjaro as well. It would be great to have a solution. I switched back to Linux 4.9 for now.

@isaacullah

I’m just chiming in to say that the solution proposed by @garyyang6 worked for me using GalliumOS (basically Xubunut) 16.04. My guess is that some conflicting files from a previous Docker install still exist in that directory, even after uninstalling with Apt.

@vineshvsv

garyyang6 — > Yes it worked after removing files from /var/lib/docker… Thank you :)

@ivanperez-keera

@garyyang6 @vineshvsv @isaacullah That eliminates existing images. If you had no backup, you’ve lost them.

Please, stop recommending that. People are going to lose their data.

tomcss, alexcpn, mwanon, ilie05, jacksonpradolima, DirkWolthuis, iamyogeshg, collins-b, cy94, MohMaz, and 22 more reacted with thumbs up emoji
yanhongwang, ShawnChambless, taogashi, ashok-arora, MohMaz, cchampou, BrandonBlanchard, august-of-wind, NMelis, and exequielrafaela reacted with heart emoji

@ivanperez-keera

WARNING: Investigate what happened. If you are on linux, look inside /var/log/syslog. If you simply erase /var/lib/docker like previous solutions suggest, you’ll lose existing images.

In my case, the log file (/var/log/syslog) pointed to a missing kernel module aufs. This was due to a kernel upgrade, so I just had to find a kernel that had that module (find /lib -iname '*aufs*'), boot linux using that kernel, load the module (modprobe aufs), and start docker (service docker start).

fxrcode, CaioPenhalver, bramhi123, NeverBehave, golangci, arnautg, yami12376, thomasks, jiangkai1984, desprit, and 20 more reacted with thumbs up emoji
slavikme reacted with hooray emoji
yanhongwang, DamianLion, phaberest, bhawna121, and brownchow reacted with heart emoji

@reegz

We experienced the same issue this morning. It appears to be related to this issue:

In our case we were able to resolve the issue by deleting the /var/run/docker.sock directory that had been created presumably as the docker service was shutting down.

@thaJeztah

I’m closing this issue because there are many possible reasons for the daemon failing to start, and the original report does not have enough information to determin that reason, but feel free to comment after I closed.

There are many possible reasons for the daemon failing to start, and (as @ivanperez-keera commented #162 (comment)), removing /var/lib/docker is often not the solution. Doing so simply wipes all your docker data, and is the equivalent to a «factory reset». While there are legitimate reasons for doing so, please don’t recommend it as a solutions to others without clearly explaining what it’s doing, and that all information (containers, images, and (more importantly) volumes) will be deleted.

If the daemon fails to start, it’s for a reason. In the example above where the required aufs modules were missing after upgrading the kernel, the daemon refuses to start because it’s missing a dependency, and is not able to use the previously selected storage-driver (also see moby/moby#15651)

If you are running into a daemon that fails to start; always make sure to check the logs (journalctl -u docker.service), as they may provide the information you need to resolve your situation.

I’m closing this issue because there are many possible reasons for the daemon failing to start, and the original report does not have enough information to determin that reason, but feel free to comment after I closed.

stowns, guylil, thomasks, Mido22, land-pack, smhjamalii, DHVKRS, PapaMadeleine2022, roccomuso, Spencatro, and 11 more reacted with thumbs up emoji
PapaMadeleine2022 and noahehall reacted with laugh emoji
PapaMadeleine2022 and noahehall reacted with hooray emoji
yanhongwang, PapaMadeleine2022, KienDangTran, and noahehall reacted with heart emoji

@ranjaykumar-singh

$systemctl start docker
Job for docker.service failed because the control process exited with error code. See «systemctl status docker.service» and «journalctl -xe» for details.

@thaJeztah

See «systemctl status docker.service» and «journalctl -xe» for details.

So, what did they show? The systemd error message prints the commands you can use to see what’s wrong.

@Aswin4070

I too have faced the same issue. It has occurred when I am trying to change my storage driver, the docker didn’t come up.
I have checked the logs from var/log/syslog and found this error:
_Error starting daemon: error initializing graphdriver: devicemapper: Can't set task name /dev/ma$_

So, I have changed it to ‘aufs’ and then the issue is resolved.

Posted here, so that it might be helpful for someone.

@magavendon

So, I have changed it to ‘aufs’ and then the issue is resolved.

What did you change to ‘aufs’?

@Jayhello

@MrMetric

I had this problem on Arch when the installed Linux version did not match the running Linux version (a frequent source of issues)

@jkanasu

Similar problem and the syslog output is below

$ sudo systemctl start docker
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

=============== Data from syslog =========================

Jan 31 15:18:43 host-192-168-0-48 systemd[1]: Starting Docker Application Container Engine...
Jan 31 15:18:43 host-192-168-0-48 dockerd[25565]: time="2018-01-31T15:18:43.799225736+05:30" level=info msg="libcontainerd: new containerd process, pid: 25571"
Jan 31 15:18:44 host-192-168-0-48 dockerd[25565]: time="2018-01-31T15:18:44.807137580+05:30" level=info msg="[graphdriver] using prior storage driver: aufs"
Jan 31 15:18:45 host-192-168-0-48 dockerd[25565]: Error starting daemon: error while opening volume store metadata database: timeout
Jan 31 15:18:45 host-192-168-0-48 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 15:18:45 host-192-168-0-48 systemd[1]: Failed to start Docker Application Container Engine.
Jan 31 15:18:45 host-192-168-0-48 systemd[1]: docker.service: Unit entered failed state.
Jan 31 15:18:45 host-192-168-0-48 systemd[1]: docker.service: Failed with result 'exit-code'.


=============== Data from journalctl =========================

$ journalctl -xe
Jan 31 15:18:43 host-192-168-0-48 systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Jan 31 15:18:43 host-192-168-0-48 dockerd[25565]: time="2018-01-31T15:18:43.799225736+05:30" level=info msg="libcontainerd: new containerd process, pid: 25571"
Jan 31 15:18:44 host-192-168-0-48 dockerd[25565]: time="2018-01-31T15:18:44.807137580+05:30" level=info msg="[graphdriver] using prior storage driver: aufs"
Jan 31 15:18:45 host-192-168-0-48 dockerd[25565]: Error starting daemon: error while opening volume store metadata database: timeout
Jan 31 15:18:45 host-192-168-0-48 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 15:18:45 host-192-168-0-48 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Jan 31 15:18:45 host-192-168-0-48 systemd[1]: docker.service: Unit entered failed state.
Jan 31 15:18:45 host-192-168-0-48 systemd[1]: docker.service: Failed with result 'exit-code'.

@Aswin4070

@jkanasu

Hi Jagadish,

I think error might be in this line of syslog.

Jan 31 15:18:45 host-192-168-0-48 dockerd[25565]: Error starting daemon: error while opening volume store metadata database: timeout

So, once check whether you have placed volume files in the source folder of the created container where you have mounted.
If not this than it might be something which is related to volumes.

@daniele-pecora

@garyyang6 is right:
removing with rm -rf /var/lib/docker solved it, but also had to prior umount /var/lib/docker/devicemapper
thanks

@MBakhshi96

i have same problem. after installing docker it gives this error :
Preparing to unpack .../docker-ce_17.12.0~ce-0~ubuntu_amd64.deb ...
Unpacking docker-ce (17.12.0~ce-0~ubuntu) ...
Setting up docker-ce (17.12.0~ce-0~ubuntu) ...
Job for docker.service failed because the control process exited with error code. See "systemctl status``docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
dpkg: error processing package docker-ce (--install):
subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (229-4ubuntu7) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
docker-ce

@reegz

@MBakhshi96 — have you tried running systemctl status as suggested in the error message?

That would provide you with the underlying cause of the error.

@MBakhshi96

@reegz it seems that docker has suspended service for iranians . stupid

@stowns

ours was failing to start because the ‘—disable-legacy-registry’ flag was removed from the daemon options in 7.12. This was obvious when viewing logs via journalctl -xe as @thaJeztah mentions.

@uzzal2k5

I found a solution by keeping all data and container that may help you all

My problem was «Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?»

after running «journalctl -u docker.service» got

Mar 10 10:08:50 uzzal dockerd[6450]: `Could not load X509 key pair (cert: "", key: ""): open : no such file or directory`
Mar 10 10:08:50 uzzal systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Mar 10 10:08:50 uzzal systemd[1]: Failed to start Docker Application Container Engine.

I took all steps describing above except delete everything from /var/lib/docker because it will delete all of my existing data.

I also create a ca.pem under /root/.docker/certs but that wouldn’t resolve my issue. So finally I do following

yum remove docker-*
rm -rf  /etc/docker
rm -rf /usr/bin/docker-*

Also this I remove everything from /var/lib/docker folder except following — folder or directories, because all of those directory / folder holds my existing data (container, images, volume etc )

containers
devicemapper
image
volumes

At finally I install docker-ce again and start it. I got all of my docker container , image and as well as volume also.

Hope someone will be benefited with this.

@hghorbani

at first step.you need to enable docker service with sudo systemctl enable docker

@ansonhorse

@hghorbani Thanks for the quick respond.
It did work when after run systemctl enable docker.service.
However, in another server, I still have this issue:

[root@VM_145_135_centos ~]# uname -a
Linux VM_145_135_centos 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

[root@VM_145_135_centos ~]# rpm -qa|grep kernel
kernel-headers-3.10.0-514.26.2.el7.x86_64
kernel-3.10.0-327.el7.x86_64
kernel-devel-3.10.0-862.3.2.el7.x86_64
kernel-devel-3.10.0-327.el7.x86_64
kernel-3.10.0-862.11.6.el7.x86_64
kernel-tools-3.10.0-514.26.2.el7.x86_64
kernel-devel-3.10.0-514.26.2.el7.x86_64
kernel-tools-libs-3.10.0-514.26.2.el7.x86_64
kernel-3.10.0-514.26.2.el7.x86_64

[root@VM_145_135_centos ~]# docker --version
Docker version 18.09.0-ce-tp5, build 9eb3d36

[root@VM_145_135_centos ~]# systemctl enable docker.service
Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.

[root@VM_145_135_centos ~]# systemctl start docker.service
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

[root@VM_145_135_centos ~]# systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: inactive (dead) (Result: exit-code) since Sun 2018-09-02 01:39:27 CST; 12s ago
     Docs: https://docs.docker.com
  Process: 15525 ExecStartPre=/usr/libexec/containerd-offline-installer /var/lib/containerd-offline-installer/containerd-shim-process.tar docker.io/docker/containerd-shim-process (code=exited, status=1/FAILURE)
Sep 02 01:39:27 VM_145_135_centos systemd[1]: docker.service: control process exited, code=exited status=1
Sep 02 01:39:27 VM_145_135_centos containerd-offline-installer[15525]: failed to dial "/run/containerd/containerd.sock": context deadline exceeded
Sep 02 01:39:27 VM_145_135_centos systemd[1]: Failed to start Docker Application Container Engine.
Sep 02 01:39:27 VM_145_135_centos systemd[1]: Unit docker.service entered failed state.
Sep 02 01:39:27 VM_145_135_centos systemd[1]: docker.service failed.
Sep 02 01:39:27 VM_145_135_centos systemd[1]: Stopped Docker Application Container Engine.

@hghorbani

create account on docker site.
run docker login
after loged in to docker account try sudo systemctl start docker

@ansonhorse

@hghorbani it didn’t work

[root@VM_145_135_centos ~]# systemctl start docker.service
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

[root@VM_145_135_centos ~]# systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: inactive (dead) (Result: exit-code) since Sun 2018-09-02 12:15:12 CST; 5s ago
     Docs: https://docs.docker.com
  Process: 23726 ExecStartPre=/usr/libexec/containerd-offline-installer /var/lib/containerd-offline-installer/containerd-shim-process.tar docker.io/docker/containerd-shim-process (code=exited, status=1/FAILURE)
 Main PID: 22805 (code=exited, status=1/FAILURE)
Sep 02 12:15:12 VM_145_135_centos systemd[1]: docker.service: control process exited, code=exited status=1
Sep 02 12:15:12 VM_145_135_centos containerd-offline-installer[23726]: failed to dial "/run/containerd/containerd.sock": context deadline exceeded
Sep 02 12:15:12 VM_145_135_centos systemd[1]: Failed to start Docker Application Container Engine.
Sep 02 12:15:12 VM_145_135_centos systemd[1]: Unit docker.service entered failed state.
Sep 02 12:15:12 VM_145_135_centos systemd[1]: docker.service failed.
Sep 02 12:15:12 VM_145_135_centos systemd[1]: Stopped Docker Application Container Engine.

I notice that the docker.service content doesn’t look similar to my another server(which docker runs fine on):

[root@VM_145_135_centos ~]# systemctl cat docker
# /usr/lib/systemd/system/docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
BindsTo=containerd.service
After=network-online.target firewalld.service
Wants=network-online.target
[Service]
# Install containerd-shim-process if it's not already installed
ExecStartPre=/usr/libexec/containerd-offline-installer /var/lib/containerd-offline-installer/containerd-shim-process.tar docker.io/docker/containerd-sh
ExecStart=/usr/bin/dockerd
ExecStopPost=/usr/bin/dockerd post-stop
TimeoutSec=0
RestartSec=2
Restart=always
# On RPM Based distributions PATH isn't defined so we define it here
# /opt/containerd/bin is in front so dockerd grabs the correct runc binary
Environment="PATH=/opt/containerd/bin:/sbin:/usr/bin:/usr/local/bin:$PATH"
[Install]
WantedBy=multi-user.target

And here is the docker.service content of another server which docker runs fine on:

➜  ~ systemctl cat docker
# /usr/lib/systemd/system/docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network-online.target firewalld.service
Wants=network-online.target
[Service]
Type=notify
# the default is not to use systemd for cgroups because the delegate issues still
# exists and systemd currently does not support the cgroup feature set required
# for containers run by docker
ExecStart=/usr/bin/dockerd
ExecReload=/bin/kill -s HUP $MAINPID
# Having non-zero Limit*s causes performance problems due to accounting overhead
# in the kernel. We recommend using cgroups to do container-local accounting.
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
# Uncomment TasksMax if your systemd version supports it.
# Only systemd 226 and above support this version.
#TasksMax=infinity
TimeoutStartSec=0
# set delegate yes so that systemd does not reset the cgroups of docker containers
Delegate=yes
# kill only the docker process, not all processes in the cgroup
KillMode=process
# restart the docker process if it exits prematurely
Restart=on-failure
StartLimitBurst=3
StartLimitInterval=60s
[Install]
WantedBy=multi-user.target

@ansonhorse

It seems that the latest version of docker (18.09.0-ce-tp5, build 9eb3d3) doesn’t work well with Centos 7(at least in my situation).
Now I install 18.06.0-ce, build 0ffa825, and it’s ok!

@hghorbani

@tommyrico81

Another solution or possible fix if running RHEL7 would be to ensure that SELinux is disabled or the directories in which SELinux is enforcing have the appropriate context labelling. The machine that I was attempting to start the docker.service on was providing the following error.

Job for docker.service failed because the control process exited with error code. See «systemctl status docker.service» and «journalctl -xe» for details

After attempting to remove the /var/lib/docker or /var/run/docker.sock and restarting docker, this did not work. Viewing the logs when running systemctl status docker.service, pointed me to the following error message.

Error starting daemon: SELinux is not supported with the overlay2 graph driver on this kernel. Either boot into a newer kernel or…abled=false)

After disabling SELinux under /etc/selinux/config then rebooting, I was able to start docker.

@beenotung

It doesn’t work for me even after removing /var/lib/docker and /var/run/docker and /var/run/docker.sock
Doesn’t work even after reinstalling the docker package

@beenotung

from the journal, it said docker.socket: Failed with result 'service-start-limit-hit'

@brainscar

Same issue on Manjaro

systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart.
systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
systemd[1]: Stopped Docker Application Container Engine.
systemd[1]: docker.service: Start request repeated too quickly.
systemd[1]: docker.service: Failed with result ‘exit-code’.
systemd[1]: Failed to start Docker Application Container Engine.

@ematta

IDK if this has already gone out or not, but I was able to fix this by editing /etc/systemd/system/docker.service.d/override.conf:

Modified to:

[Unit]
Description=Docker Service
After=network.target docker.socket
[Service]
Environment="DOCKER_OPTS=-H fd:// --data-root /mnt/data/docker --storage-driver=aufs --bip=172.17.42.1/16 --raw-logs --log-opt max-size=500m --log-opt max-file=10"
ExecStart=
ExecStart=/usr/bin/dockerd $DOCKER_OPTS
Restart=on-failure
RestartSec=1s
TimeoutSec=20

The main change is changing -g to --data-root in $DOCKER_OPTS and changing docker daemon $DOCKER_OPTS to dockerd $DOCKER_OPTS

Hope this helps.

@Routhinator

In my instance this error was produced by a trailing comma on the last line of the json object in daemon.json.

Overall, this error is non-informative and digging through syslog is necessary because either docker or systemd fail to properly pass variables through to the systemd output, so we get nonsense messages like Failed with result 'exit-code' and Result was RESULT

This ticket should be renamed Docker does not pass error output to systemd properly and the devs should be working on fixing that.

@luizhpriotto

Form me dont resolve remove /var/lib/docker. My default kernel on grub was a enterprise kernel, I changed to unbreak kernel and the problem was resolved.

@surbhitayal

I faced the same issue. Go through the logs of ‘ journalctl -u docker.service’. For me the first few lines read as below:
Oct 11 18:20:27 osboxes systemd[1]: Starting Docker Application Container Engine…
Oct 11 18:20:27 osboxes dockerd-current[22625]: time=»2018-10-11T18:20:27.509894419+01:00″ level=warning msg=»could not change group /var/run/docker.sock to docker: group as the group does not exist»
Oct 11 18:20:27 osboxes dockerd-current[22625]: time=»2018-10-11T18:20:27.528388575+01:00″ level=info msg=»libcontainerd: new containerd process, pid: 22633″
Oct 11 18:20:28 osboxes dockerd-current[22625]: time=»2018-10-11T18:20:28.567184177+01:00″ level=warning msg=»overlay2: the backing xfs filesystem is formatted without
Oct 11 18:20:30 osboxes dockerd-current[22625]: Error starting daemon: SELinux is not supported with the overlay2 graph driver on this kernel. Either boot into a newer
Oct 11 18:20:30 osboxes systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE

First I created a group docker, which did not solve the problem. Next, I disabled the SELinux in /etc/sysconfig/docker. This helped and I running systemctl start docker.service worked successfully.

@RamanjaneyuluIdavalapati

Problem was solved by restarting the machine in my case.

@f-ld

@bidai541

Same error. In my case, the deamon file is wrong, so i solved this by delete /etc/systemd/system/docker.service.d file. Be carefor.

@berkant

These are all workarounds. What the rooting heck is causing this problem? Anybody knows?

@zblan

just execute below and don’t remove data：
yum remove docker-*
rm -rf /etc/docker
rm -rf /usr/bin/docker-*
Don‘t remove otherthings。

@obetron

Remove /var/lib/docker (rm -rf /var/lib/docker). Restart Docker solved the problem.

not recommended!! you’ll lose your containers!!!

@thaJeztah

not recommended!! you’ll lose your containers!!!

Agreed; also see my earlier comment: it’s recommended to try and understand why the daemon fails to start by checking the logs #162 (comment)

@Adrianocs

After remove the file:
/etc/systemd/system/docker.service.d/override.conf
and execute this commands:
systemctl reset-failed docker.service
systemctl start docker.service
The docker service was started.
Tks…

@lisn0

in my case i commented everything in /etc/systemd/system/docker.service.d/noiptables.conf
then reloaded and restarted and it worked

@msource1

In my case, CentOS 7.x — I noticed that the issue was not the docker.service itself, but a dependency:

**Sep 02 12:15:12 VM_145_135_centos containerd-offline-installer[23726]: failed to dial "/run/containerd/containerd.sock": context deadline exceeded**

Then noticed that it was bind to docker.service:

# nano /usr/lib/systemd/system/docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
**BindsTo=containerd.service**

I commented the this line, and docker startup without further issues.

**#BindsTo=containerd.service**

@aeciovc

@vasconce7os

It seems that the latest version of docker (18.09.0-ce-tp5, build 9eb3d3) doesn’t work well with Centos 7(at least in my situation).
Now I install 18.06.0-ce, build 0ffa825, and it’s ok!

I have the same problem in CentOS 7.5 and a solution like it.

I remove docker yum remove docker-ce*
I installed by twice time using the repository, following doc instructions and I listed versions with this command: yum list docker-ce --showduplicates | sort -r and I chose version 18.03.1.ce-1.el7.centos, my twice time comand install was yum install docker-ce-18.03.1.ce-1.el7.centos

@ivanperez-keera

These are just workarounds that do not really find out the source of the problem. Nobody will ever learn to fix the problem this way, and people could really lose their work.

See #162 (comment), #162 (comment) and #162 (comment).

Could someone please prevent others from commenting?

@thaJeztah

Yes, let me lock this thread; if you arrive here, please refer to #162 (comment), which may help you find the reason for docker not starting in your situation.

@docker
docker

locked and limited conversation to collaborators

Nov 26, 2018

Источник

Just tried to install docker on my Ubuntu 16.04, and I get the error below. Any suggestions what is wrong and how to fix it?

Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2017-07-28 12:39:11 CEST; 9ms ago
     Docs: https://docs.docker.com
  Process: 15533 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
 Main PID: 15533 (code=exited, status=1/FAILURE)

Jul 28 12:39:11 jonas-X555LAB systemd[1]: Failed to start Docker Application Container Engine.
Jul 28 12:39:11 jonas-X555LAB systemd[1]: docker.service: Unit entered failed state.
Jul 28 12:39:11 jonas-X555LAB systemd[1]: docker.service: Failed with result 'exit-code'.
dpkg: error processing package docker-ce (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for systemd (229-4ubuntu19) ...
Processing triggers for ureadahead (0.100.0-19) ...
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

I followed this guide:
https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-16-04

$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
$ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
sudo apt-get update

$ sudo apt-cache policy docker-ce
docker-ce:
  Installed: 17.06.0~ce-0~ubuntu
  Candidate: 17.06.0~ce-0~ubuntu
  Version table:
 *** 17.06.0~ce-0~ubuntu 500
        500 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages
        500 https://download.docker.com/linux/ubuntu xenial/edge amd64 Packages
        100 /var/lib/dpkg/status
     17.05.0~ce-0~ubuntu-xenial 500
        500 https://download.docker.com/linux/ubuntu xenial/edge amd64 Packages
     17.04.0~ce-0~ubuntu-xenial 500
        500 https://download.docker.com/linux/ubuntu xenial/edge amd64 Packages
     17.03.2~ce-0~ubuntu-xenial 500
        500 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages
     17.03.1~ce-0~ubuntu-xenial 500
        500 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages
     17.03.0~ce-0~ubuntu-xenial 500
        500 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages

$ sudo apt-get install -y docker-ce

On this same machine, I have a Linux Mint 17.3 installation on which docker worked just fine. Using same home directory as before on LM17.3.

Here are some specs:

$ inxi -fs
CPU:       Dual core Intel Core i3-4005U (-HT-MCP-) cache: 3072 KB 
           clock speeds: max: 1600 MHz 1: 799 MHz 2: 799 MHz 3: 799 MHz 4: 799 MHz
           CPU Flags: abm acpi aes aperfmperf apic arat arch_perfmon avx avx2 bmi1 bmi2 bts clflush cmov
           constant_tsc cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept erms est f16c flexpriority fma fpu fsgsbase
           fxsr ht invpcid lahf_lm lm mca mce mmx monitor movbe msr mtrr nonstop_tsc nopl nx pae pat pbe pcid
           pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pts rdrand rdtscp rep_good sdbg sep smep ss
           sse sse2 sse4_1 sse4_2 ssse3 syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi
           vpid xsave xsaveopt xtopology xtpr
Sensors:   System Temperatures: cpu: 40.5C mobo: N/A
           Fan Speeds (in rpm): cpu: 2800

Источник

Hello,

I did a fresh install of docker but I can’t start the docker.service.

I reinstalled the docker package:

I then enabled the service:

systemctl enable docker.service

When I try to start the service:

systemctl start docker.service

I get the error below:

Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details

This is the output from «journalctl -xeu docker.service»:

The process' exit code is 'exited' and its exit status is 1.
Jul 03 00:31:46 ws systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Jul 03 00:31:46 ws systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 16696 and the job result is failed.
Jul 03 00:31:46 ws systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit docker.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jul 03 00:31:46 ws systemd[1]: Stopped Docker Application Container Engine.
░░ Subject: A stop job for unit docker.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit docker.service has finished.
░░
░░ The job identifier is 16781 and the job result is done.
Jul 03 00:31:46 ws systemd[1]: docker.service: Start request repeated too quickly.
Jul 03 00:31:46 ws systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Jul 03 00:31:46 ws systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 16781 and the job result is failed.

Output from «systemctl status docker.service»:

× docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Sat 2021-07-03 00:31:46 CEST; 2min 39s ago
TriggeredBy: × docker.socket
       Docs: https://docs.docker.com
    Process: 126666 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
   Main PID: 126666 (code=exited, status=1/FAILURE)
        CPU: 180ms

Jul 03 00:31:46 ws systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jul 03 00:31:46 ws systemd[1]: Stopped Docker Application Container Engine.
Jul 03 00:31:46 ws systemd[1]: docker.service: Start request repeated too quickly.
Jul 03 00:31:46 ws systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 03 00:31:46 ws systemd[1]: Failed to start Docker Application Container Engine.

Output from «journalctl -r -g docker»:

-- Journal begins at Sat 2021-06-19 01:26:00 CEST, ends at Sat 2021-07-03 00:31:46 CEST. --
Jul 03 00:31:46 ws kernel: audit: type=1130 audit(1625265106.658:1571): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:31:46 ws systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
Jul 03 00:31:46 ws systemd[1]: Failed to start Docker Application Container Engine.
Jul 03 00:31:46 ws systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 03 00:31:46 ws systemd[1]: docker.service: Start request repeated too quickly.
Jul 03 00:31:46 ws audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 00:31:46 ws audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 00:31:46 ws systemd[1]: Stopped Docker Application Container Engine.
Jul 03 00:31:46 ws systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jul 03 00:31:46 ws kernel: audit: type=1130 audit(1625265106.315:1570): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:31:46 ws audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 03 00:31:46 ws systemd[1]: Failed to start Docker Application Container Engine.
Jul 03 00:31:46 ws systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 03 00:31:46 ws systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 00:31:46 ws dockerd[126666]: failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptable>
Jul 03 00:31:45 ws dockerd[126666]: time="2021-07-03T00:31:45.260705702+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock  <nil>>
Jul 03 00:31:45 ws dockerd[126666]: time="2021-07-03T00:31:45.260066865+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock  <nil>>
Jul 03 00:31:45 ws dockerd[126686]: time="2021-07-03T00:31:45.253299809+02:00" level=info msg=serving... address=/var/run/docker/containerd/containerd.sock
Jul 03 00:31:45 ws dockerd[126686]: time="2021-07-03T00:31:45.253275809+02:00" level=info msg=serving... address=/var/run/docker/containerd/containerd.sock.ttrpc
Jul 03 00:31:45 ws dockerd[126686]: time="2021-07-03T00:31:45.253246659+02:00" level=info msg=serving... address=/var/run/docker/containerd/containerd-debug.sock
Jul 03 00:31:45 ws dockerd[126686]: time="2021-07-03T00:31:45.252429603+02:00" level=info msg="skip loading plugin "io.containerd.snapshotter.v1.zfs"..." error="path /var/lib/docker/containerd/>
Jul 03 00:31:45 ws dockerd[126686]: time="2021-07-03T00:31:45.252225334+02:00" level=info msg="skip loading plugin "io.containerd.snapshotter.v1.btrfs"..." error="path /var/lib/docker/container>
Jul 03 00:31:45 ws dockerd[126666]: time="2021-07-03T00:31:45.217608967+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock  <nil>>
Jul 03 00:31:45 ws systemd[1]: Starting Docker Application Container Engine...
Jul 03 00:31:45 ws kernel: audit: type=1131 audit(1625265105.158:1569): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:31:45 ws kernel: audit: type=1130 audit(1625265105.158:1568): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:31:45 ws systemd[1]: Stopped Docker Application Container Engine.
Jul 03 00:31:45 ws audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 00:31:45 ws audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 00:31:45 ws systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jul 03 00:31:44 ws kernel: audit: type=1130 audit(1625265104.815:1567): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:31:44 ws audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 03 00:31:44 ws systemd[1]: Failed to start Docker Application Container Engine.
Jul 03 00:31:44 ws systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 03 00:31:44 ws systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 00:31:44 ws dockerd[126560]: failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptable>
Jul 03 00:31:43 ws dockerd[126560]: time="2021-07-03T00:31:43.758701681+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock  <nil>>
Jul 03 00:31:43 ws dockerd[126560]: time="2021-07-03T00:31:43.758189224+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock  <nil>>
Jul 03 00:31:43 ws dockerd[126580]: time="2021-07-03T00:31:43.752511094+02:00" level=info msg=serving... address=/var/run/docker/containerd/containerd.sock
Jul 03 00:31:43 ws dockerd[126580]: time="2021-07-03T00:31:43.752485144+02:00" level=info msg=serving... address=/var/run/docker/containerd/containerd.sock.ttrpc
Jul 03 00:31:43 ws dockerd[126580]: time="2021-07-03T00:31:43.752452874+02:00" level=info msg=serving... address=/var/run/docker/containerd/containerd-debug.sock
Jul 03 00:31:43 ws dockerd[126580]: time="2021-07-03T00:31:43.751569328+02:00" level=info msg="skip loading plugin "io.containerd.snapshotter.v1.zfs"..." error="path /var/lib/docker/containerd/>
Jul 03 00:31:43 ws dockerd[126580]: time="2021-07-03T00:31:43.751342230+02:00" level=info msg="skip loading plugin "io.containerd.snapshotter.v1.btrfs"..." error="path /var/lib/docker/container>
Jul 03 00:31:43 ws dockerd[126560]: time="2021-07-03T00:31:43.715700818+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock  <nil>>
Jul 03 00:31:43 ws systemd[1]: Starting Docker Application Container Engine...
Jul 03 00:31:43 ws kernel: audit: type=1131 audit(1625265103.658:1566): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:31:43 ws kernel: audit: type=1130 audit(1625265103.658:1565): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:31:43 ws systemd[1]: Stopped Docker Application Container Engine.
Jul 03 00:31:43 ws audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 00:31:43 ws audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 00:31:43 ws systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jul 03 00:31:43 ws kernel: audit: type=1130 audit(1625265103.382:1564): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:31:43 ws audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 03 00:31:43 ws systemd[1]: Failed to start Docker Application Container Engine.
Jul 03 00:31:43 ws systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 03 00:31:43 ws systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 00:31:43 ws dockerd[126441]: failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptable>
Jul 03 00:31:42 ws dockerd[126441]: time="2021-07-03T00:31:42.330096770+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock  <nil>>
Jul 03 00:31:42 ws dockerd[126441]: time="2021-07-03T00:31:42.329477924+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock  <nil>>
Jul 03 00:31:42 ws dockerd[126461]: time="2021-07-03T00:31:42.322787517+02:00" level=info msg=serving... address=/var/run/docker/containerd/containerd.sock
Jul 03 00:31:42 ws dockerd[126461]: time="2021-07-03T00:31:42.322739667+02:00" level=info msg=serving... address=/var/run/docker/containerd/containerd.sock.ttrpc
Jul 03 00:31:42 ws dockerd[126461]: time="2021-07-03T00:31:42.322669338+02:00" level=info msg=serving... address=/var/run/docker/containerd/containerd-debug.sock
Jul 03 00:31:42 ws dockerd[126461]: time="2021-07-03T00:31:42.319082446+02:00" level=info msg="skip loading plugin "io.containerd.snapshotter.v1.zfs"..." error="path /var/lib/docker/containerd/>
Jul 03 00:31:42 ws dockerd[126461]: time="2021-07-03T00:31:42.318793147+02:00" level=info msg="skip loading plugin "io.containerd.snapshotter.v1.btrfs"..." error="path /var/lib/docker/container>
Jul 03 00:31:42 ws dockerd[126441]: time="2021-07-03T00:31:42.276829328+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock  <nil>>
Jul 03 00:31:42 ws systemd[1]: Starting Docker Application Container Engine...
Jul 03 00:31:42 ws systemd[1]: Listening on Docker Socket for the API.
Jul 03 00:31:42 ws systemd[1]: Starting Docker Socket for the API.
Jul 03 00:31:42 ws polkitd[829]: Operator of unix-session:1 successfully authenticated as unix-user:denis to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for syst>
Jul 03 00:31:34 ws polkitd[829]: Operator of unix-session:1 successfully authenticated as unix-user:denis to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-unit-files for>
Jul 03 00:31:21 ws sudo[126291]:    denis : TTY=pts/1 ; PWD=/home/denis/code/vastgoed/etl ; USER=root ; COMMAND=/usr/bin/pacman -S docker
Jul 03 00:30:41 ws sudo[126220]:    denis : TTY=pts/1 ; PWD=/home/denis/code/vastgoed/etl ; USER=root ; COMMAND=/usr/bin/rm -rf /run/docker.sock
Jul 03 00:30:33 ws sudo[126201]:    denis : TTY=pts/1 ; PWD=/home/denis/code/vastgoed/etl ; USER=root ; COMMAND=/usr/bin/rm -rf /var/lib/docker
Jul 03 00:30:24 ws sudo[126176]:    denis : TTY=pts/1 ; PWD=/home/denis/code/vastgoed/etl ; USER=root ; COMMAND=/usr/bin/rm -rf /run/docker
Jul 03 00:30:16 ws sudo[126132]:    denis : TTY=pts/1 ; PWD=/home/denis/code/vastgoed/etl ; USER=root ; COMMAND=/usr/bin/pacman -Rns docker
Jul 03 00:22:20 ws sudo[124944]:    denis : TTY=pts/1 ; PWD=/home/denis/code/vastgoed/etl ; USER=root ; COMMAND=/usr/bin/dockerd
Jul 03 00:22:11 ws kernel: audit: type=1130 audit(1625264531.407:1280): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:22:11 ws systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
Jul 03 00:22:11 ws systemd[1]: Failed to start Docker Application Container Engine.
Jul 03 00:22:11 ws systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 03 00:22:11 ws systemd[1]: docker.service: Start request repeated too quickly.
Jul 03 00:22:11 ws audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 00:22:11 ws audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 00:22:11 ws systemd[1]: Stopped Docker Application Container Engine.
Jul 03 00:22:11 ws systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jul 03 00:22:11 ws kernel: audit: type=1130 audit(1625264531.073:1279): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Jul 03 00:22:11 ws audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 03 00:22:11 ws systemd[1]: Failed to start Docker Application Container Engine.
Jul 03 00:22:11 ws systemd[1]: docker.service: Failed with result 'exit-code'.

What is causing the issue?

Last edited by djenis (2021-07-03 09:40:23)

Источник

[root@localhost ~]# systemctl restart docker

Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details.

[root@localhost ~]#

[root@localhost ~]# journalctl -xe

Oct 18 12:57:24 localhost.localdomain systemd[1]: Starting Docker Application Container Engine.

— Subject: Unit docker.service has begun start-up

— Defined-By: systemd

— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

—

— Unit docker.service has begun starting up.

Oct 18 12:57:24 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:24.671424476+05:30″

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.742590614+05:30″

Oct 18 12:57:25 localhost.localdomain systemd[1]: Device dev-disk-byx2duuid-7acdd2e7x2dc6c7x

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.775414831+05:30″

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.785846416+05:30″

Oct 18 12:57:25 localhost.localdomain systemd[1]: docker.service: main process exited, code=exi

Oct 18 12:57:25 localhost.localdomain systemd[1]: Failed to start Docker Application Container

— Subject: Unit docker.service has failed

— Defined-By: systemd

— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

—

— Unit docker.service has failed.

—

— The result is failed.

Oct 18 12:57:25 localhost.localdomain systemd[1]: Unit docker.service entered failed state.

Oct 18 12:57:25 localhost.localdomain systemd[1]: docker.service failed.

Oct 18 12:57:25 localhost.localdomain polkitd[763]: Unregistered Authentication Agent for unix-

lines 2668-2690/2690 (END)

[root@localhost ~]# systemctl status -l docker.service

? docker.service – Docker Application Container Engine

Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)

Active: failed (Result: exit-code) since Tue 2016-10-18 12:57:25 IST; 6min ago

Docs: https://docs.docker.com

Process: 3547 ExecStart=/usr/bin/dockerd (code=exited, status=1/FAILURE)

Main PID: 3547 (code=exited, status=1/FAILURE)

Oct 18 12:57:24 localhost.localdomain systemd[1]: Starting Docker Application Container Engine…

Oct 18 12:57:24 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:24.671424476+05:30″ level=info msg=”libcontainerd: new containerd process, pid: 3551″

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.742590614+05:30″ level=warning msg=”devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `–storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section.”

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.775414831+05:30″ level=warning msg=”devmapper: Base device already exists and has filesystem xfs on it. User specified filesystem  will be ignored.”

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.785846416+05:30″ level=fatal msg=”Error starting daemon: error initializing graphdriver: ”/var/lib/docker” contains several valid graphdrivers: devicemapper, overlay; Please cleanup or explicitly choose storage driver (-s <DRIVER>)”

Oct 18 12:57:25 localhost.localdomain systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE

Oct 18 12:57:25 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine.

Oct 18 12:57:25 localhost.localdomain systemd[1]: Unit docker.service entered failed state.

Oct 18 12:57:25 localhost.localdomain systemd[1]: docker.service failed.

play

Docker Advance Tutorial | Part 1 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 2 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 3 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 4 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 5 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 6 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 7 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 8 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 9 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 10 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 11 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 13 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 14 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 15 out 16 | — By DevOpsSchool

play

Docker Advance Tutorial | Part 16 out 16 | — By DevOpsSchool

  • Author
  • Recent Posts

Rajesh Kumar

Mentor for DevOps — DevSecOps — SRE — Cloud — Container & Micorservices at Cotocus

Join my following certification courses…
— DevOps Certified Professionals (DCP)
— Site Reliability Engineering Certified Professionals (SRECP)
— Master in DevOps Engineering (MDE)
— DevSecOps Certified Professionals (DSOCP)
URL — https://www.devopsschool.com/certification/

My Linkedin — https://www.linkedin.com/in/rajeshkumarin
My Email — contact@DevOpsSchool.com

Rajesh Kumar

Источник

1 answer to this question.

Related Questions In Docker

  • All categories

  • ChatGPT
    (2)

  • Apache Kafka
    (84)

  • Apache Spark
    (596)

  • Azure
    (131)

  • Big Data Hadoop
    (1,907)

  • Blockchain
    (1,673)

  • C#
    (141)

  • C++
    (271)

  • Career Counselling
    (1,060)

  • Cloud Computing
    (3,446)

  • Cyber Security & Ethical Hacking
    (147)

  • Data Analytics
    (1,266)

  • Database
    (855)

  • Data Science
    (75)

  • DevOps & Agile
    (3,575)

  • Digital Marketing
    (111)

  • Events & Trending Topics
    (28)

  • IoT (Internet of Things)
    (387)

  • Java
    (1,247)

  • Kotlin
    (8)

  • Linux Administration
    (389)

  • Machine Learning
    (337)

  • MicroStrategy
    (6)

  • PMP
    (423)

  • Power BI
    (516)

  • Python
    (3,188)

  • RPA
    (650)

  • SalesForce
    (92)

  • Selenium
    (1,569)

  • Software Testing
    (56)

  • Tableau
    (608)

  • Talend
    (73)

  • TypeSript
    (124)

  • Web Development
    (3,002)

  • Ask us Anything!
    (66)

  • Others
    (1,929)

  • Mobile Development
    (263)

Subscribe to our Newsletter, and get personalized recommendations.

Already have an account? Sign in.

Источник

Skip to navigation
Skip to main content

Red Hat Customer Portal

Infrastructure and Management

  • Red Hat Enterprise Linux

  • Red Hat Virtualization

  • Red Hat Identity Management

  • Red Hat Directory Server

  • Red Hat Certificate System

  • Red Hat Satellite

  • Red Hat Subscription Management

  • Red Hat Update Infrastructure

  • Red Hat Insights

  • Red Hat Ansible Automation Platform

Cloud Computing

  • Red Hat OpenShift

  • Red Hat CloudForms

  • Red Hat OpenStack Platform

  • Red Hat OpenShift Container Platform

  • Red Hat OpenShift Data Science

  • Red Hat OpenShift Online

  • Red Hat OpenShift Dedicated

  • Red Hat Advanced Cluster Security for Kubernetes

  • Red Hat Advanced Cluster Management for Kubernetes

  • Red Hat Quay

  • OpenShift Dev Spaces

  • Red Hat OpenShift Service on AWS

Storage

  • Red Hat Gluster Storage

  • Red Hat Hyperconverged Infrastructure

  • Red Hat Ceph Storage

  • Red Hat OpenShift Data Foundation

Runtimes

  • Red Hat Runtimes

  • Red Hat JBoss Enterprise Application Platform

  • Red Hat Data Grid

  • Red Hat JBoss Web Server

  • Red Hat Single Sign On

  • Red Hat support for Spring Boot

  • Red Hat build of Node.js

  • Red Hat build of Thorntail

  • Red Hat build of Eclipse Vert.x

  • Red Hat build of OpenJDK

  • Red Hat build of Quarkus

Integration and Automation

  • Red Hat Process Automation

  • Red Hat Process Automation Manager

  • Red Hat Decision Manager

All Products

Issue

  • We are trying to setup docker but after starting it the service fails with:

    # systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─hosts.conf
   Active: failed (Result: exit-code) since Fri 2018-04-20 14:41:30 CEST; 16s ago
     Docs: http://docs.docker.com
  Process: 8699 ExecStart=/usr/bin/docker $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $BLOCK_REGISTRY $INSECURE_REGISTRY (code=exited, status=125)
 Main PID: 8699 (code=exited, status=125)

Apr 20 14:41:30 hostname docker[8699]: top         Display the running processes of a container
Apr 20 14:41:30 hostname docker[8699]: unpause     Unpause all processes within one or more containers
Apr 20 14:41:30 hostname docker[8699]: update      Update configuration of one or more containers
Apr 20 14:41:30 hostname docker[8699]: version     Show the Docker version information
Apr 20 14:41:30 hostname docker[8699]: wait        Block until one or more containers stop, then print their exit codes
Apr 20 14:41:30 hostname docker[8699]: Run 'docker COMMAND --help' for more information on a command.
Apr 20 14:41:30 hostname systemd[1]: docker.service: main process exited, code=exited, status=125/n/a
Apr 20 14:41:30 hostname systemd[1]: Failed to start Docker Application Container Engine.
Apr 20 14:41:30 hostname systemd[1]: Unit docker.service entered failed state.
Apr 20 14:41:30 hostname systemd[1]: docker.service failed.

Environment

  • Red Hat Enterprise Linux (RHEL) 7.4
  • Docker service

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

Источник
root@staging:~# sudo systemctl unmask docker
Removed /etc/systemd/system/docker.service.
root@staging:~# sudo systemctl start docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

I needed to run this to solve a docker issue. Docker kept crashing after 1-2 hours after I run docker-compose up. So I tried to follow the steps provided here.

https://stackoverflow.com/questions/64163450/unable-to-docker-compose-up-any-project

When I run this, I get:

root@staging:~# start docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Then, when logging by running systemctl status docker.service:

docker.service - LSB: Create lightweight, portable, self-sufficient containers.
     Loaded: loaded (/etc/init.d/docker; generated)
     Active: failed (Result: exit-code) since Wed 2021-09-08 18:13:30 UTC; 1min 37s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 329588 ExecStart=/etc/init.d/docker start (code=exited, status=1/FAILURE)

Sep 08 18:13:30 staging.shane.com systemd[1]: Starting LSB: Create lightweight, portable, self-sufficient containers....
Sep 08 18:13:30 staging.shane.com docker[329588]:  * /usr/bin/dockerd not present or not executable
Sep 08 18:13:30 staging.shane.com systemd[1]: docker.service: Control process exited, code=exited, status=1/FAILURE
Sep 08 18:13:30 staging.shane.com systemd[1]: docker.service: Failed with result 'exit-code'.
Sep 08 18:13:30 staging.shane.com systemd[1]: Failed to start LSB: Create lightweight, portable, self-sufficient containers..

And the other log:

    Sep 08 18:17:13 staging.shane.com kernel: br-d107a0b785af: port 1(veth2eb79a3) entered blocking state
Sep 08 18:17:13 staging.shane.com kernel: br-d107a0b785af: port 1(veth2eb79a3) entered forwarding state
Sep 08 18:17:13 staging.shane.com kernel: eth2: renamed from vetha6ad44f
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: veth87721c2: Gained carrier
Sep 08 18:17:13 staging.shane.com kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth87721c2: link becomes ready
Sep 08 18:17:13 staging.shane.com kernel: br-d86eed067d4f: port 1(veth87721c2) entered blocking state
Sep 08 18:17:13 staging.shane.com kernel: br-d86eed067d4f: port 1(veth87721c2) entered forwarding state
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: veth8794b2b: Lost carrier
Sep 08 18:17:13 staging.shane.com kernel: br-5ee6c619ebc6: port 3(veth8794b2b) entered disabled state
Sep 08 18:17:13 staging.shane.com kernel: veth9694d7a: renamed from eth0
Sep 08 18:17:13 staging.shane.com systemd-udevd[332558]: ethtool: autonegotiation is unset or enabled, the speed and duplex a>
Sep 08 18:17:13 staging.shane.com networkd-dispatcher[463]: WARNING:Unknown index 780021 seen, reloading interface list
Sep 08 18:17:13 staging.shane.com systemd-udevd[332558]: ethtool: autonegotiation is unset or enabled, the speed and duplex a>
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: veth8794b2b: Link DOWN
Sep 08 18:17:13 staging.shane.com kernel: br-5ee6c619ebc6: port 3(veth8794b2b) entered disabled state
Sep 08 18:17:13 staging.shane.com kernel: device veth8794b2b left promiscuous mode
Sep 08 18:17:13 staging.shane.com kernel: br-5ee6c619ebc6: port 3(veth8794b2b) entered disabled state
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: rtnl: received neighbor for link '780022' we don't know about, ig>
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: rtnl: received neighbor for link '780022' we don't know about, ig>
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: veth2eb79a3: Lost carrier
Sep 08 18:17:13 staging.shane.com kernel: br-d107a0b785af: port 1(veth2eb79a3) entered disabled state
Sep 08 18:17:13 staging.shane.com kernel: veth8058d46: renamed from eth1
Sep 08 18:17:13 staging.shane.com systemd-udevd[332558]: ethtool: autonegotiation is unset or enabled, the speed and duplex a>
Sep 08 18:17:13 staging.shane.com networkd-dispatcher[463]: WARNING:Unknown index 780023 seen, reloading interface list
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: veth2eb79a3: Link DOWN
Sep 08 18:17:13 staging.shane.com kernel: br-d107a0b785af: port 1(veth2eb79a3) entered disabled state
Sep 08 18:17:13 staging.shane.com kernel: device veth2eb79a3 left promiscuous mode
Sep 08 18:17:13 staging.shane.com kernel: br-d107a0b785af: port 1(veth2eb79a3) entered disabled state
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: rtnl: received neighbor for link '780024' we don't know about, ig>
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: rtnl: received neighbor for link '780024' we don't know about, ig>
Sep 08 18:17:13 staging.shane.com systemd-udevd[332558]: veth8058d46: Failed to get link config: No such device
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: veth87721c2: Lost carrier
Sep 08 18:17:13 staging.shane.com kernel: br-d86eed067d4f: port 1(veth87721c2) entered disabled state
Sep 08 18:17:13 staging.shane.com kernel: vetha6ad44f: renamed from eth2
Sep 08 18:17:13 staging.shane.com systemd-udevd[332558]: ethtool: autonegotiation is unset or enabled, the speed and duplex a>
Sep 08 18:17:13 staging.shane.com networkd-dispatcher[463]: WARNING:Unknown index 780025 seen, reloading interface list
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: veth87721c2: Link DOWN
Sep 08 18:17:13 staging.shane.com kernel: br-d86eed067d4f: port 1(veth87721c2) entered disabled state
Sep 08 18:17:13 staging.shane.com kernel: device veth87721c2 left promiscuous mode
Sep 08 18:17:13 staging.shane.com kernel: br-d86eed067d4f: port 1(veth87721c2) entered disabled state
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: rtnl: received neighbor for link '780026' we don't know about, ig>
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: rtnl: received neighbor for link '780026' we don't know about, ig>
Sep 08 18:17:13 staging.shane.com systemd-udevd[332558]: vetha6ad44f: Failed to get link config: No such device
Sep 08 18:17:13 staging.shane.com systemd-networkd[809323]: br-d107a0b785af: Lost carrier
Sep 08 18:17:20 staging.shane.com sshd[333537]: Unable to negotiate with 141.98.12.129 port 58900: no matching key exchange m>
Sep 08 18:17:30 staging.shane.com sshd[333542]: Unable to negotiate with 141.98.12.129 port 57548: no matching key exchange m>

Источник

Понравилась статья? Поделить с друзьями:
  • Docker php fpm error log
  • Docker msbuild error msb1009 project file does not exist
  • Docker mosquito error address not available
  • Docker logs error level
  • Docker login error response from daemon