Deutsches Docker Forum

Please or Register to create posts and topics.

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

Hi,

Ich wollte gerade zum Testen Docker unter Debian 9 installieren, doch es kommt zum Fehler:

 

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’.

->Ich finde den Fehler nicht.

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 8
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’.

Ich habe gerade Collabora Online installiert, um es in Nextcloud zu integrieren, und alles war gut. Jetzt funktioniert plötzlich nichts mehr, es wurde nichts in der Konfiguration geändert, ich kann nicht herausfinden, was nicht richtig ist?

Wie kann ich Docker wieder Starten?

  1. Starte Docker wie immer
  2. Versuche Weiterhin Dokumente in Nextcloud zu öffnen.
  3. Klicke "OK" bei “Well, this is embarrassing, we cannot connect to your document. Please try again.”
  4. Click “OK” bei “Service is unavailable. Please try again later and report to your administrator if the issue persists.”
  5. Gehen Sie immer wieder zu Schritt 3 zurück, bis Sie schließlich die Meldung "Failed to load the document. Please ensure the file type is supported and not corrupted, and try again."
  6. Klicke auf "OK" und verlasse das Menü "Dateien".
  7. Starte Docker (Den Service nicht das Image) neu.
  8. Fehler sollte behoben sein.
Thencent has reacted to this post.
Thencent
Zitat von Tobias am Oktober 8, 2021, 23:30 Uhr
  1. Starte Docker wie immer
  2. Versuche Weiterhin Dokumente in Nextcloud zu öffnen.
  3. Klicke "OK" bei “Well, this is embarrassing, we cannot connect to your document. Please try again.”
  4. Click “OK” bei “Service is unavailable. Please try again later and report to your administrator if the issue persists.”
  5. Gehen Sie immer wieder zu Schritt 3 zurück, bis Sie schließlich die Meldung "Failed to load the document. Please ensure the file type is supported and not corrupted, and try again."
  6. Klicke auf "OK" und verlasse das Menü "Dateien".
  7. Starte Docker (Den Service nicht das Image) neu.
  8. Fehler sollte behoben sein.

Danke das hat geklappt. Auch wenn mir diese Lösung komisch erscheint.

Tobias has reacted to this post.
Tobias