Docker plugin - After the last update it does not start

    • OMV 4.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Seeing this too :(

      Source Code

      1. Nov 08 08:52:43 omv4 systemd[1]: Starting Docker Application Container Engine...
      2. -- Subject: Unit docker.service has begun start-up
      3. -- Defined-By: systemd
      4. -- Support: https://www.debian.org/support
      5. --
      6. -- Unit docker.service has begun starting up.
      7. Nov 08 08:52:43 omv4 dockerd[11288]: Failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd
      8. Nov 08 08:52:43 omv4 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
      9. Nov 08 08:52:43 omv4 systemd[1]: Failed to start Docker Application Container Engine.
      10. -- Subject: Unit docker.service has failed
      11. -- Defined-By: systemd
      12. -- Support: https://www.debian.org/support
      13. --
      14. -- Unit docker.service has failed.
      15. --
      16. -- The result is failed.
      17. Nov 08 08:52:43 omv4 systemd[1]: docker.service: Unit entered failed state.
      18. Nov 08 08:52:43 omv4 systemd[1]: docker.service: Failed with result 'exit-code'.
      Display All
    • sardaukar wrote:

      Managed to fix it by replacing "-H fd://" with "-H unix://" in /etc/systemd/system/docker.service.d/openmediavault.conf
      #metoo

      thanks for the tip. Could docker to run again :thumbsup:
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • g2_ufo wrote:

      still error Failed to stop docker.socket: Unit docker.socket not loaded.

      DId the change but still getting the error:
      Can you please explain the whole steps like disable plugin, modify the line, enable plugin?

      Still getting:

      Source Code
      Edit Source Code
      1. Error #0:
      2. OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl stop 'docker.socket' 2>&1' with exit code '5': Failed to stop docker.socket: Unit docker.socket not loaded. in /usr/share/php/openmediavault/system/process.inc:182
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 5)
      5. #1 /usr/share/php/openmediavault/system/systemctl.inc(153): OMV\System\SystemCtl->exec('stop', NULL, false)
      6. #2 /usr/share/omvdocker/Utils.php(92): OMV\System\SystemCtl->stop()
      7. #3 /usr/share/omvdocker/Utils.php(531): OMVModuleDockerUtil::stopDockerService()
      8. #4 /usr/share/openmediavault/engined/rpc/docker.inc(1205): OMVModuleDockerUtil::changeDockerSettings(Array, 42005, '/srv/dev-disk-b...')
      9. #5 [internal function]: OMVRpcServiceDocker->setSettings(Array, Array)
      10. #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setSettings', Array, Array)
      12. #8 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'setSettings', Array, Array, 1)
      13. #9 {main}


      openmediavaulkt.conf looks like:

      Source Code
      Edit Source Code
      1. [Service]
      2. EnvironmentFile=-/etc/default/docker
      3. ExecStart=
      4. ExecStart=/usr/bin/dockerd -H unix:// $DOCKER_OPTS \
      5. $OMVDOCKER_API \
      6. $OMVDOCKER_IMAGE_PATH


      Thanks for your help!
    • For me the problem the mentioned change fixed the issue that the service did not start.

      So now the docker service is OK again.

      The openmediavaut-docker-gui is still having problems but all my containers are running again.
      Maybe you have the same problem?

      For me after changing the conf-file I had to run:
      service stop docker
      systemctl daemon-reload
      service start docker

      And to check if that helped
      docker container ls
    • der.nicc wrote:

      For me the problem the mentioned change fixed the issue that the service did not start.

      So now the docker service is OK again.

      The openmediavaut-docker-gui is still having problems but all my containers are running again.
      Maybe you have the same problem?

      For me after changing the conf-file I had to run:
      service stop docker
      systemctl daemon-reload
      service start docker

      And to check if that helped
      docker container ls
      Thanks for your help but it's still not working:

      container ls:
      CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

      When enabling plugin i get:

      Source Code

      1. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl stop 'docker.socket' 2>&1' with exit code '5': Failed to stop docker.socket: Unit docker.socket not loaded.
      Is there a way to completly and clenly uninstall docker?
    • I did an uninstall and reinstall for the openmediavault-docker-gui via the "Erweiterungen" page in the omv-gui. Should be "Add-Ons" or similar.
      But that threw some errors for the openmediavault-docker-gui ("Bad Gateway").

      Maybe you could try it as well.
      Uninstall
      Reinstall
      "service docker stop"
      make the change to the conf-file
      "systemctl daemon-reload"
      "service docker start"
      "docker container ls" (after giving some time to start the containers and if no errors accured)

      At least this is what I did after getting the same errors as you before.
      But I am not sure what exactly helped here.
    • Getting this when reinstalling plugin:

      Source Code

      1. Reading package lists...
      2. Building dependency tree...
      3. Reading state information...
      4. The following additional packages will be installed:
      5. docker-ce imagemagick-6-common libcurl3 libfftw3-double3 liblcms2-2
      6. liblqr-1-0 libmagickcore-6.q16-3 libmagickwand-6.q16-3 libopenjp2-7
      7. omvextras-common php-curl php-imagick php-symfony-class-loader
      8. php-symfony-polyfill-apcu php7.0-curl
      9. Suggested packages:
      10. libfftw3-bin libfftw3-dev liblcms2-utils libmagickcore-6.q16-3-extra
      11. Recommended packages:
      12. aufs-tools cgroupfs-mount | cgroup-lite git pigz ghostscript gsfonts
      13. ttf-dejavu-core
      14. The following NEW packages will be installed:
      15. docker-ce imagemagick-6-common libcurl3 libfftw3-double3 liblcms2-2
      16. liblqr-1-0 libmagickcore-6.q16-3 libmagickwand-6.q16-3 libopenjp2-7
      17. omvextras-common openmediavault-docker-gui php-curl php-imagick
      18. php-symfony-class-loader php-symfony-polyfill-apcu php7.0-curl
      19. 0 upgraded, 16 newly installed, 0 to remove and 0 not upgraded.
      20. Need to get 0 B/21.3 MB of archives.
      21. After this operation, 99.0 MB of additional disk space will be used.
      22. Selecting previously unselected package liblqr-1-0:amd64.
      23. (Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 83159 files and directories currently installed.)
      24. Preparing to unpack .../00-liblqr-1-0_0.4.2-2+b2_amd64.deb ...
      25. Unpacking liblqr-1-0:amd64 (0.4.2-2+b2) ...
      26. Selecting previously unselected package libfftw3-double3:amd64.
      27. Preparing to unpack .../01-libfftw3-double3_3.3.5-3_amd64.deb ...
      28. Unpacking libfftw3-double3:amd64 (3.3.5-3) ...
      29. Selecting previously unselected package liblcms2-2:amd64.
      30. Preparing to unpack .../02-liblcms2-2_2.8-4+deb9u1_amd64.deb ...
      31. Unpacking liblcms2-2:amd64 (2.8-4+deb9u1) ...
      32. Selecting previously unselected package libopenjp2-7:amd64.
      33. Preparing to unpack .../03-libopenjp2-7_2.1.2-1.1+deb9u2_amd64.deb ...
      34. Unpacking libopenjp2-7:amd64 (2.1.2-1.1+deb9u2) ...
      35. Selecting previously unselected package imagemagick-6-common.
      36. Preparing to unpack .../04-imagemagick-6-common_8%3a6.9.7.4+dfsg-11+deb9u6_all.deb ...
      37. Unpacking imagemagick-6-common (8:6.9.7.4+dfsg-11+deb9u6) ...
      38. Selecting previously unselected package libmagickcore-6.q16-3:amd64.
      39. Preparing to unpack .../05-libmagickcore-6.q16-3_8%3a6.9.7.4+dfsg-11+deb9u6_amd64.deb ...
      40. Unpacking libmagickcore-6.q16-3:amd64 (8:6.9.7.4+dfsg-11+deb9u6) ...
      41. Selecting previously unselected package libmagickwand-6.q16-3:amd64.
      42. Preparing to unpack .../06-libmagickwand-6.q16-3_8%3a6.9.7.4+dfsg-11+deb9u6_amd64.deb ...
      43. Unpacking libmagickwand-6.q16-3:amd64 (8:6.9.7.4+dfsg-11+deb9u6) ...
      44. Selecting previously unselected package docker-ce.
      45. Preparing to unpack .../07-docker-ce_5%3a18.09.0~3-0~debian-stretch_amd64.deb ...
      46. Unpacking docker-ce (5:18.09.0~3-0~debian-stretch) ...
      47. Selecting previously unselected package libcurl3:amd64.
      48. Preparing to unpack .../08-libcurl3_7.52.1-5+deb9u8_amd64.deb ...
      49. Unpacking libcurl3:amd64 (7.52.1-5+deb9u8) ...
      50. Selecting previously unselected package php-symfony-polyfill-apcu.
      51. Preparing to unpack .../09-php-symfony-polyfill-apcu_1.2.0-1_all.deb ...
      52. Unpacking php-symfony-polyfill-apcu (1.2.0-1) ...
      53. Selecting previously unselected package php-symfony-class-loader.
      54. Preparing to unpack .../10-php-symfony-class-loader_2.8.7+dfsg-1.3+deb9u1_all.deb ...
      55. Unpacking php-symfony-class-loader (2.8.7+dfsg-1.3+deb9u1) ...
      56. Selecting previously unselected package omvextras-common.
      57. Preparing to unpack .../11-omvextras-common_4.0.1_all.deb ...
      58. Unpacking omvextras-common (4.0.1) ...
      59. Selecting previously unselected package php7.0-curl.
      60. Preparing to unpack .../12-php7.0-curl_7.0.30-0+deb9u1_amd64.deb ...
      61. Unpacking php7.0-curl (7.0.30-0+deb9u1) ...
      62. Selecting previously unselected package php-curl.
      63. Preparing to unpack .../13-php-curl_1%3a7.0+49_all.deb ...
      64. Unpacking php-curl (1:7.0+49) ...
      65. Selecting previously unselected package php-imagick.
      66. Preparing to unpack .../14-php-imagick_3.4.3~rc2-2_amd64.deb ...
      67. Unpacking php-imagick (3.4.3~rc2-2) ...
      68. Preparing to unpack .../15-openmediavault-docker-gui_4.0.1_all.deb ...
      69. Unpacking openmediavault-docker-gui (4.0.1) ...
      70. Setting up imagemagick-6-common (8:6.9.7.4+dfsg-11+deb9u6) ...
      71. Setting up docker-ce (5:18.09.0~3-0~debian-stretch) ...
      72. update-alternatives: using /usr/bin/dockerd-ce to provide /usr/bin/dockerd (dockerd) in auto mode
      73. Created symlink /etc/systemd/system/multi-user.target.wants/docker.service -> /lib/systemd/system/docker.service.
      74. Setting up libopenjp2-7:amd64 (2.1.2-1.1+deb9u2) ...
      75. Setting up liblcms2-2:amd64 (2.8-4+deb9u1) ...
      76. Setting up libcurl3:amd64 (7.52.1-5+deb9u8) ...
      77. Setting up php7.0-curl (7.0.30-0+deb9u1) ...
      78. Creating config file /etc/php/7.0/mods-available/curl.ini with new version
      79. Setting up libfftw3-double3:amd64 (3.3.5-3) ...
      80. Processing triggers for php7.0-fpm (7.0.30-0+deb9u1) ...
      81. Setting up liblqr-1-0:amd64 (0.4.2-2+b2) ...
      82. Processing triggers for libc-bin (2.24-11+deb9u3) ...
      83. Setting up php-symfony-polyfill-apcu (1.2.0-1) ...
      84. Processing triggers for openmediavault (4.1.13-1) ...
      85. Restarting engine daemon ...
      86. Cannot create socket to [localhost]:2812 -- Connection refused
      87. Setting up libmagickcore-6.q16-3:amd64 (8:6.9.7.4+dfsg-11+deb9u6) ...
      88. Setting up php-curl (1:7.0+49) ...
      89. Setting up php-symfony-class-loader (2.8.7+dfsg-1.3+deb9u1) ...
      90. Setting up libmagickwand-6.q16-3:amd64 (8:6.9.7.4+dfsg-11+deb9u6) ...
      91. Setting up omvextras-common (4.0.1) ...
      92. Setting up php-imagick (3.4.3~rc2-2) ...
      93. Processing triggers for openmediavault (4.1.13-1) ...
      94. Updating file permissions ...
      95. Purging internal cache ...
      96. Restarting engine daemon ...
      97. Cannot create socket to [localhost]:2812 -- Connection refused
      98. Setting up openmediavault-docker-gui (4.0.1) ...
      99. sed: can't read /etc/default/docker: No such file or directory
      100. dpkg: error processing package openmediavault-docker-gui (--configure):
      101. subprocess installed post-installation script returned error exit status 2
      102. Processing triggers for libc-bin (2.24-11+deb9u3) ...
      103. Processing triggers for openmediavault (4.1.13-1) ...
      104. Restarting engine daemon ...
      105. Cannot create socket to [localhost]:2812 -- Connection refused
      106. Errors were encountered while processing:
      107. openmediavault-docker-gui
      Display All
      No luck with your steps :(

      Thanks for your hint
    • Hi,

      I have the same problem.

      Docker is started, all containers are up and running. Docker can not be activated in the GUI.

      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl stop 'docker.socket' 2>&1' with exit code '5': Failed to stop docker.socket: Unit docker.socket not loaded.
    • SEWA wrote:

      Hi,

      I have the same problem.

      Docker is started, all containers are up and running. Docker can not be activated in the GUI.

      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl stop 'docker.socket' 2>&1' with exit code '5': Failed to stop docker.socket: Unit docker.socket not loaded.
      Actually none of my dockers are running.
    • SEWA wrote:

      Hi,

      I have the same problem.

      Docker is started, all containers are up and running. Docker can not be activated in the GUI.

      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl stop 'docker.socket' 2>&1' with exit code '5': Failed to stop docker.socket: Unit docker.socket not loaded.

      The same here, docker is up and running with all the containers but I cannot manage it with the GUI due to that error.

      It seems that omv cannot execute: systemctl stop 'docker.socket' but is ok if you try with systemctl stop 'docker' from cli

      The post was edited 1 time, last by Ciccius: Adding infos ().

    • My test machine is still working. I will need to try to replicate this. No need to update that people's systems aren't working until I look into this more. No idea what update did this but it isn't the plugin.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • Users Online 1

      1 Guest

    • Tags