Docker Community Forums

Share and learn in the Docker community.

Failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd


(Ini0r) #1

Hi,

new to docker here, noticed that docker crashed but can’t restart it ?

Debian 9
ii docker-ce 5:18.09.0~3-0~debian-stretch
ii docker-ce-cli 5:18.09.0~3-0~debian-stretch

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.

journalctl -xe

– Unit docker.service has finished shutting down.
Nov 10 13:20:58 edgar systemd[1]: Starting Docker Application Container Engine…
– Subject: Unit docker.service has begun start-up
– Defined-By: systemd
– Support:

– Unit docker.service has begun starting up.
Nov 10 13:20:58 edgar dockerd[14611]: Failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd
Nov 10 13:20:58 edgar systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Nov 10 13:20:58 edgar systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support:

– Unit docker.service has failed.

– The result is failed.
Nov 10 13:20:58 edgar systemd[1]: docker.service: Unit entered failed state.
Nov 10 13:20:58 edgar systemd[1]: docker.service: Failed with result ‘exit-code’.
Nov 10 13:21:00 edgar systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Nov 10 13:21:00 edgar systemd[1]: Stopped Docker Application Container Engine.
– Subject: Unit docker.service has finished shutting down
– Defined-By: systemd
– Support:

– Unit docker.service has finished shutting down.
Nov 10 13:21:00 edgar systemd[1]: Starting Docker Application Container Engine…
– Subject: Unit docker.service has begun start-up
– Defined-By: systemd
– Support:

– Unit docker.service has begun starting up.
Nov 10 13:21:00 edgar dockerd[14640]: Failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd
Nov 10 13:21:00 edgar systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Nov 10 13:21:00 edgar systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support:

– Unit docker.service has failed.

– The result is failed.
Nov 10 13:21:00 edgar systemd[1]: docker.service: Unit entered failed state.
Nov 10 13:21:00 edgar systemd[1]: docker.service: Failed with result ‘exit-code’.
Nov 10 13:21:02 edgar systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Nov 10 13:21:02 edgar systemd[1]: Stopped Docker Application Container Engine.
– Subject: Unit docker.service has finished shutting down
– Defined-By: systemd
– Support:

– Unit docker.service has finished shutting down.
Nov 10 13:21:02 edgar systemd[1]: docker.service: Start request repeated too quickly.
Nov 10 13:21:02 edgar systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support:

– Unit docker.service has failed.

– The result is failed.
Nov 10 13:21:02 edgar systemd[1]: docker.service: Unit entered failed state.
Nov 10 13:21:02 edgar systemd[1]: docker.service: Failed with result ‘exit-code’.

->Can’t even locate where is the error ?

systemctl status docker

● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/docker.service.d
└─DeviceMapper.conf
Active: failed (Result: exit-code) since Sat 2018-11-10 13:21:02 CET; 1min 57s ago
Docs: https://docs.docker.com
Process: 14640 ExecStart=/usr/bin/dockerd --storage-driver=devicemapper -H fd:// (code=exited, status=1/FAILURE)
Main PID: 14640 (code=exited, status=1/FAILURE)
CPU: 81ms

Nov 10 13:21:00 edgar systemd[1]: docker.service: Unit entered failed state.
Nov 10 13:21:00 edgar systemd[1]: docker.service: Failed with result ‘exit-code’.
Nov 10 13:21:02 edgar systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Nov 10 13:21:02 edgar systemd[1]: Stopped Docker Application Container Engine.
Nov 10 13:21:02 edgar systemd[1]: docker.service: Start request repeated too quickly.
Nov 10 13:21:02 edgar systemd[1]: Failed to start Docker Application Container Engine.
Nov 10 13:21:02 edgar systemd[1]: docker.service: Unit entered failed state.
Nov 10 13:21:02 edgar systemd[1]: docker.service: Failed with result ‘exit-code’.

I just installed Collabora Online to integrate with Nextcloud and all was fine, then now suddenly nothing works, nothing was changed in config, can’t find what is not correct ?

How to make docker start again ?

PS : followed this to deploy : https://www.linuxbabe.com/cloud-storage/integrate-collabora-online-server-nextcloud-ubuntu-16-04

Thanks in advance for any help.


Failed to start docker.service: Unit docker.socket not found after kernel update on lubuntu
(Saulg) #2

Hi iniOr,

I had the same issue under Ubuntu 18.04.

My problem was caused by the fact that I had in the past overrode the value of ExecStart of the docker service. I had copied the original ExecStart including -H fd:// which after recent update stopped working. I’ve noticed that the orignal docker.service file now contains -H unix:// instead. I can see in the data You’ve sent that Your service is using -H fd:// as well.

So the solution that worked for me was to edit the docker’s systemd unit file and change the ExecStart:
sudo systemctl edit docker.service

The value that I had to override was ExecStart and I had to change fd:// to unix://:
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H unix://

Best Regards,
saulg


(Vierer) #3

Last reply helped me on one installation. Same steps on a seccond installation failed again complainging about unsupported devicemapper driver.


(Ini0r) #4

Thanks for your helpfull reply Saulg, I followed your instructions and now my Docker is now working again.

For the record after restarting Docker, I got this issue in Collabora and Nextcloud :

Now everything is fixed, thanks for your help :slight_smile: