Installing docker creates an error

    • OMV 5.x (beta)
    • 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.



      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: 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: 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: 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: 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: 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: 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: debian.org/support-- -- A start job for unit systemd-tmpfiles-clean.service has finished successfully.-- -- The job identifier is 1681.

      The post was edited 1 time, last by 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: 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: 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: 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: 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: 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: 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: debian.org/support-- -- A start job for unit systemd-tmpfiles-clean.service has finished successfully.-- -- The job identifier is 1681.

      The post was edited 1 time, last by cabbie: Duplicate post ().

      Post by cabbie ().

      This post was deleted by the author themselves: Duplicate ().
    • 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 - github.com/OpenMediaVault-Plug…99cb3eb1de6ff28cb8a0a1cee
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      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.

      Source Code

      1. root@omvbhal:/sharedfolders/media# journalctl -n20 -u docker.service --no-pager
      2. -- Logs begin at Mon 2019-11-18 14:26:04 EST, end at Mon 2019-11-18 14:47:46 EST. --
      3. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.055862168-05:00" level=info msg="Starting up"
      4. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.058083921-05:00" level=info msg="parsed scheme: \"unix\"" module=grpc
      5. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.058117340-05:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
      6. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.058154212-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" module=grpc
      7. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.058182464-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
      8. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.059296994-05:00" level=info msg="parsed scheme: \"unix\"" module=grpc
      9. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.059318209-05:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
      10. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.059336081-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" module=grpc
      11. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.059348777-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
      12. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.062857448-05:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
      13. Nov 18 14:35:22 omvbhal.local dockerd[5956]: failed to start daemon: error while opening volume store metadata database: no such device
      14. Nov 18 14:35:22 omvbhal.local systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
      15. Nov 18 14:35:22 omvbhal.local systemd[1]: docker.service: Failed with result 'exit-code'.
      16. Nov 18 14:35:22 omvbhal.local systemd[1]: Failed to start Docker Application Container Engine.
      17. Nov 18 14:35:24 omvbhal.local systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
      18. Nov 18 14:35:24 omvbhal.local systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
      19. Nov 18 14:35:24 omvbhal.local systemd[1]: Stopped Docker Application Container Engine.
      20. Nov 18 14:35:24 omvbhal.local systemd[1]: docker.service: Start request repeated too quickly.
      21. Nov 18 14:35:24 omvbhal.local systemd[1]: docker.service: Failed with result 'exit-code'.
      22. Nov 18 14:35:24 omvbhal.local systemd[1]: Failed to start Docker Application Container Engine.
      Display All

      The post was edited 1 time, last by siddharth_bhal: attaching logs ().

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

      siddharth_bhal wrote:

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

      Source Code

      1. root@omvbhal:/sharedfolders/media# journalctl -n20 -u docker.service --no-pager
      2. -- Logs begin at Mon 2019-11-18 14:26:04 EST, end at Mon 2019-11-18 14:47:46 EST. --
      3. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.055862168-05:00" level=info msg="Starting up"
      4. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.058083921-05:00" level=info msg="parsed scheme: \"unix\"" module=grpc
      5. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.058117340-05:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
      6. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.058154212-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" module=grpc
      7. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.058182464-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
      8. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.059296994-05:00" level=info msg="parsed scheme: \"unix\"" module=grpc
      9. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.059318209-05:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
      10. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.059336081-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" module=grpc
      11. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.059348777-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
      12. Nov 18 14:35:22 omvbhal.local dockerd[5956]: time="2019-11-18T14:35:22.062857448-05:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
      13. Nov 18 14:35:22 omvbhal.local dockerd[5956]: failed to start daemon: error while opening volume store metadata database: no such device
      14. Nov 18 14:35:22 omvbhal.local systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
      15. Nov 18 14:35:22 omvbhal.local systemd[1]: docker.service: Failed with result 'exit-code'.
      16. Nov 18 14:35:22 omvbhal.local systemd[1]: Failed to start Docker Application Container Engine.
      17. Nov 18 14:35:24 omvbhal.local systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
      18. Nov 18 14:35:24 omvbhal.local systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
      19. Nov 18 14:35:24 omvbhal.local systemd[1]: Stopped Docker Application Container Engine.
      20. Nov 18 14:35:24 omvbhal.local systemd[1]: docker.service: Start request repeated too quickly.
      21. Nov 18 14:35:24 omvbhal.local systemd[1]: docker.service: Failed with result 'exit-code'.
      22. Nov 18 14:35:24 omvbhal.local systemd[1]: Failed to start Docker Application Container Engine.
      Display All
    • siddharth_bhal wrote:

      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.

      siddharth_bhal wrote:

      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.

      siddharth_bhal wrote:

      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.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

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