Installing docker creates an error

  • Hello, I am running OMV 5.0.14. When I go to OMV-extras and click 'Install Docker' the install fails.


    Opera Näyttökuva_2019-11-18_172121_192.168.1.236.png


    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.

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

  • Yep, there is something going on with the docker package that causes it to not start on first install. apt-get -f install should fix it. And while I don't think omv-extras should have to do something to fix, I did add apt-get -f install to omv-extras 5.1.5 - https://github.com/OpenMediaVa…99cb3eb1de6ff28cb8a0a1cee

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • @ryecoaaron I am facing same problem. For me apt-get -f install isn't working as well.


    I am getting following error when trying to start dockerd:
    Nov 18 14:35:22 omvbhal.local dockerd[5956]: failed to start daemon: error while opening volume store metadata database: no such device


    I thinks its a different issues. Little more context: I am using unionfs on OMV 5 and yesterday upgraded uinonfs plugin to 5.0.1. After upgrade, I observed sharedfolders/xyz were properly mounted and showing same data in /srv/<pool id>/xyz. But today I restarted system and since then I am facing docker installation issue as well as /sharedfolders aren't being populated.


    I believe, path provided as "Docker Storage" in ui has to be a shared folder.
    I have tried using "Docker storage" path on the lines of:
    - /sharedfolders/dockers
    - /srv/<pool id>/dockers
    - /srv/dev-by-disk-name-xxx/dockers (used direct path to remove unionfs issues)


    I also have tried apt-get purge openmediavault-omvextrasorg and reinstalling docker-ce, but same problem.


    Haven't tried to use "Docker Storage" as /var/lib/docker since OMV installation is on USB drive.


  • Here is how I resolved: As I suspected it was "Docker Storage" path issue. I assume updating Docker Storage path from UI wasn't working for me. I manually edit the file /etc/docker/daemon.json and updated location.

  • path provided as "Docker Storage" in ui has to be a shared folder.

    Nope. It is an absolute path anywhere on the system. I wouldn't use a mergerfs pool for this though.

    I am getting following error when trying to start dockerd:
    Nov 18 14:35:22 omvbhal.local dockerd[5956]: failed to start daemon: error while opening volume store metadata database: no such device

    Sounds like your path was invalid.


    I manually edit the file /etc/docker/daemon.json and updated location.

    What did you edit it to? You should be able to put the same path in the field in omv-extras.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • @ryecoaaron Now I am no longer using mergefs pool for docker storage. I updated path in /etc/docker/daemon.json to /srv/dev-by-disk-name-xxx/dockers which is working great for me. I suspect updating path in field in omv-extras wasn't updating /etc/docker/daemon.json for me earlier but now it does.

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

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!