I am using zfs. I looked into /etc/docker/daemon.json, it reads:
"data-root": "/sharedfolders/docker"
which the same as what reads in the omv-extras docker startup screen.
Forcing the install did not help.
Beiträge von cabbie
-
-
root@openmediavault:~# systemctl status docker.service● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-11-18 17:19:29 EET; 5min ago Docs: https://docs.docker.com Process: 17613 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE) Main PID: 17613 (code=exited, status=1/FAILURE)Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.Nov 18 17:19:29 openmediavault.local systemd[1]: Stopped Docker Application Container Engine.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Start request repeated too quickly.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Failed with result 'exit-code'.Nov 18 17:19:29 openmediavault.local systemd[1]: Failed to start Docker Application Container Engine.root@openmediavault:~# journalctl -xeNov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Start request repeated too quickly.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Failed with result 'exit-code'.-- Subject: Unit failed-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- The unit docker.service has entered the 'failed' state with result 'exit-code'.Nov 18 17:19:29 openmediavault.local systemd[1]: Failed to start Docker Application Container Engine.-- Subject: A start job for unit docker.service has failed-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- A start job for unit docker.service has finished with a failure.-- -- The job identifier is 1601 and the job result is failed.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.-- Subject: Unit failed-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.Nov 18 17:20:30 openmediavault.local kernel: perf: interrupt took too long (2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500Nov 18 17:23:43 openmediavault.local systemd[1]: Starting Cleanup of Temporary Directories...-- Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- A start job for unit systemd-tmpfiles-clean.service has begun execution.-- -- The job identifier is 1681.Nov 18 17:23:43 openmediavault.local systemd[1]: systemd-tmpfiles-clean.service: Succeeded.-- Subject: Unit succeeded-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state.Nov 18 17:23:43 openmediavault.local systemd[1]: Started Cleanup of Temporary Directories.-- Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- A start job for unit systemd-tmpfiles-clean.service has finished successfully.-- -- The job identifier is 1681.
-
Hello, I am running OMV 5.0.14. When I go to OMV-extras and click 'Install Docker' the install fails.
After this the docker status is 'Installed and not running'. Latest updates have been installed and the system rebooted.
root@openmediavault:~# systemctl status docker.service● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-11-18 17:19:29 EET; 5min ago Docs: https://docs.docker.com Process: 17613 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE) Main PID: 17613 (code=exited, status=1/FAILURE)Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.Nov 18 17:19:29 openmediavault.local systemd[1]: Stopped Docker Application Container Engine.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Start request repeated too quickly.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Failed with result 'exit-code'.Nov 18 17:19:29 openmediavault.local systemd[1]: Failed to start Docker Application Container Engine.root@openmediavault:~# journalctl -xeNov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Start request repeated too quickly.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.service: Failed with result 'exit-code'.-- Subject: Unit failed-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- The unit docker.service has entered the 'failed' state with result 'exit-code'.Nov 18 17:19:29 openmediavault.local systemd[1]: Failed to start Docker Application Container Engine.-- Subject: A start job for unit docker.service has failed-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- A start job for unit docker.service has finished with a failure.-- -- The job identifier is 1601 and the job result is failed.Nov 18 17:19:29 openmediavault.local systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.-- Subject: Unit failed-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.Nov 18 17:20:30 openmediavault.local kernel: perf: interrupt took too long (2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500Nov 18 17:23:43 openmediavault.local systemd[1]: Starting Cleanup of Temporary Directories...-- Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- A start job for unit systemd-tmpfiles-clean.service has begun execution.-- -- The job identifier is 1681.Nov 18 17:23:43 openmediavault.local systemd[1]: systemd-tmpfiles-clean.service: Succeeded.-- Subject: Unit succeeded-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state.Nov 18 17:23:43 openmediavault.local systemd[1]: Started Cleanup of Temporary Directories.-- Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- A start job for unit systemd-tmpfiles-clean.service has finished successfully.-- -- The job identifier is 1681.