Latest Docker plugin update

    • Latest Docker plugin update

      Just updated my OMV installation (4.1.13-1 - using 4.18.0-0.bpo.1-amd64 Kernel), and now my Docker plugin won't run. The following error is generated when attempting to enable the plugin:

      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.

      and details:

      Error #0: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:182Stack trace:#0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 5)#1 /usr/share/php/openmediavault/system/systemctl.inc(153): OMV\System\SystemCtl->exec('stop', NULL, false)#2 /usr/share/omvdocker/Utils.php(92): OMV\System\SystemCtl->stop()#3 /usr/share/omvdocker/Utils.php(531): OMVModuleDockerUtil::stopDockerService()#4 /usr/share/openmediavault/engined/rpc/docker.inc(1205): OMVModuleDockerUtil::changeDockerSettings(Array, 42005, '')#5 [internal function]: OMVRpcServiceDocker->setSettings(Array, Array)#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setSettings', Array, Array)#8 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'setSettings', Array, Array, 1)#9 {main}

      systemctl status docker.service generates the following:

      docker.service - Docker Application Container Engine
      Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
      Drop-In: /etc/systemd/system/docker.service.d
      └─openmediavault.conf
      Active: failed (Result: exit-code) since Wed 2018-11-07 21:21:54 EST; 4s ago
      Docs: docs.docker.com
      Process: 2843 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS $OMVDOCKER_API $OMVDOCKER_IMAGE_PATH (code=exited, status=1/FAILURE)
      Main PID: 2843 (code=exited, status=1/FAILURE)
      CPU: 65ms

      Nov 07 21:21:52 omv4 systemd[1]: docker.service: Unit entered failed state.
      Nov 07 21:21:52 omv4 systemd[1]: docker.service: Failed with result 'exit-code'.
      Nov 07 21:21:54 omv4 systemd[1]: docker.service: Service hold-off time over, scheduling restart.
      Nov 07 21:21:54 omv4 systemd[1]: Stopped Docker Application Container Engine.
      Nov 07 21:21:54 omv4 systemd[1]: docker.service: Start request repeated too quickly.
      Nov 07 21:21:54 omv4 systemd[1]: Failed to start Docker Application Container Engine.
      Nov 07 21:21:54 omv4 systemd[1]: docker.service: Unit entered failed state.
      Nov 07 21:21:54 omv4 systemd[1]: docker.service: Failed with result 'exit-code'.

      I've rebooted the server, and tried a few troubleshooting steps listed in other threads, to no avail. What am I missing? Currently my whole home automation system and all media services are currently dead due to this issue. Please help!
    • Similar here. There was three udates for docker available under the update management tab, and after the updates, I get this error now. Saw another user on the discord today with docker erros also, so it appears not to be isolated.

      Source Code

      1. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; docker images 2>&1' with exit code '1': Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
      Update edit: after running "systemctl status docker.service" the output is the same as stickynickel posted.

      The post was edited 3 times, last by kmal808 ().

    • Ruschi wrote:

      did nobody test this plugin before..
      The plugin hasn't been updated in a year... This is something else. My test machine is still working. I will need to try to replicate this.
      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!
    • ryecoaaron wrote:


      The plugin hasn't been updated in a year...
      There was an update. I saw it today and after the update docker didn't start anymore. Only by changing the fix, posted here something with ..UNIX:... and a reboot started docker and the containers again
      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
    • @ryecoaaron if this helps

      Source Code

      1. systemctl status docker.service
      2. ● docker.service - Docker Application Container Engine
      3. Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
      4. Drop-In: /etc/systemd/system/docker.service.d
      5. └─openmediavault.conf
      6. Active: failed (Result: exit-code) since Thu 2018-11-08 12:34:46 GMT; 2min 22s ago
      7. Docs: https://docs.docker.com
      8. Process: 9956 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS $OMVDOCKER_API $OMVDOCKER_IMAGE_PATH (code=exited, stat Main PID: 9956 (code=exited, status=1/FAILURE)
      9. CPU: 521ms
      10. Nov 08 12:34:44 omv-pi systemd[1]: Failed to start Docker Application Container Engine.
      11. Nov 08 12:34:44 omv-pi systemd[1]: docker.service: Unit entered failed state.
      12. Nov 08 12:34:44 omv-pi systemd[1]: docker.service: Failed with result 'exit-code'.
      13. Nov 08 12:34:46 omv-pi systemd[1]: docker.service: Service hold-off time over, scheduling restart.
      14. Nov 08 12:34:46 omv-pi systemd[1]: Stopped Docker Application Container Engine.
      15. Nov 08 12:34:46 omv-pi systemd[1]: docker.service: Start request repeated too quickly.
      16. Nov 08 12:34:46 omv-pi systemd[1]: Failed to start Docker Application Container Engine.
      17. Nov 08 12:34:46 omv-pi systemd[1]: docker.service: Unit entered failed state.
      18. Nov 08 12:34:46 omv-pi systemd[1]: docker.service: Failed with result 'exit-code'.
      Display All



      Source Code

      1. journalctl -xe
      2. --
      3. -- The result is failed.
      4. Nov 08 12:34:46 omv-pi systemd[1]: docker.service: Unit entered failed state.
      5. Nov 08 12:34:46 omv-pi systemd[1]: docker.service: Failed with result 'exit-code'.
      6. Nov 08 12:35:01 omv-pi CRON[10010]: pam_unix(cron:session): session opened for user root by (uid=0)
      7. Nov 08 12:35:01 omv-pi CRON[10011]: pam_unix(cron:session): session opened for user root by (uid=0)
      8. Nov 08 12:35:01 omv-pi CRON[10018]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
      9. Nov 08 12:35:01 omv-pi CRON[10019]: (root) CMD (for i in `pgrep "ftpd|nfsiod|smbd|afpd|cnid"` ; do ionice -c1 -p $i ; doNov 08 12:35:01 omv-pi CRON[10010]: pam_unix(cron:session): session closed for user root
      10. Nov 08 12:35:02 omv-pi CRON[10011]: pam_unix(cron:session): session closed for user root
      11. Nov 08 12:35:40 omv-pi postfix/qmgr[29460]: CEB371E02BB: from=<root@omv-pi.localdomain>, size=705, nrcpt=1 (queue activeNov 08 12:35:40 omv-pi postfix/qmgr[29460]: 06C4D1E031E: from=<openmediavault-webgui@omv-pi.localdomain>, size=975, nrcpNov 08 12:35:40 omv-pi postfix/smtp[10043]: fatal: missing host information in server description: :25
      12. Nov 08 12:35:41 omv-pi postfix/smtp[10044]: fatal: missing host information in server description: :25
      13. Nov 08 12:35:41 omv-pi postfix/qmgr[29460]: warning: private/smtp socket: malformed response
      14. Nov 08 12:35:41 omv-pi postfix/qmgr[29460]: warning: transport smtp failure -- see a previous warning/fatal/panic logfilNov 08 12:35:41 omv-pi postfix/master[1837]: warning: process /usr/lib/postfix/sbin/smtp pid 10043 exit status 1
      15. Nov 08 12:35:41 omv-pi postfix/master[1837]: warning: /usr/lib/postfix/sbin/smtp: bad command startup -- throttling
      16. Nov 08 12:35:42 omv-pi postfix/qmgr[29460]: warning: private/smtp socket: malformed response
      17. Nov 08 12:35:42 omv-pi postfix/qmgr[29460]: warning: transport smtp failure -- see a previous warning/fatal/panic logfilNov 08 12:35:42 omv-pi postfix/master[1837]: warning: process /usr/lib/postfix/sbin/smtp pid 10044 exit status 1
      18. Nov 08 12:35:42 omv-pi postfix/error[10047]: CEB371E02BB: to=<root@omv-pi.localdomain>, orig_to=<root>, relay=none, delaNov 08 12:35:42 omv-pi postfix/error[10047]: 06C4D1E031E: to=<admin@omv-pi.localdomain>, orig_to=<admin>, relay=none, deNov 08 12:36:01 omv-pi CRON[10106]: pam_unix(cron:session): session opened for user root by (uid=0)
      19. Nov 08 12:36:01 omv-pi CRON[10110]: (root) CMD (for i in `pgrep "ftpd|nfsiod|smbd|afpd|cnid"` ; do ionice -c1 -p $i ; doNov 08 12:36:01 omv-pi CRON[10106]: pam_unix(cron:session): session closed for user root
      20. Nov 08 12:37:01 omv-pi CRON[10145]: pam_unix(cron:session): session opened for user root by (uid=0)
      21. Nov 08 12:37:01 omv-pi CRON[10149]: (root) CMD (for i in `pgrep "ftpd|nfsiod|smbd|afpd|cnid"` ; do ionice -c1 -p $i ; doNov 08 12:37:01 omv-pi CRON[10145]: pam_unix(cron:session): session closed for user root
      Display All
      However, if I run journalctl -xe a second time the output is this;

      Source Code

      1. journalctl -xe
      2. Nov 08 12:39:01 omv-pi systemd[1]: Started Clean php session files.
      3. -- Subject: Unit phpsessionclean.service has finished start-up
      4. -- Defined-By: systemd
      5. -- Support: https://www.debian.org/support
      6. --
      7. -- Unit phpsessionclean.service has finished starting up.
      8. --
      9. -- The start-up result is done.
      10. Nov 08 12:39:01 omv-pi CRON[10282]: pam_unix(cron:session): session opened for user root by (uid=0)
      11. Nov 08 12:39:01 omv-pi CRON[10280]: pam_unix(cron:session): session opened for user root by (uid=0)
      12. Nov 08 12:39:01 omv-pi CRON[10293]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ];
      13. Nov 08 12:39:01 omv-pi CRON[10281]: pam_unix(cron:session): session opened for user root by (uid=0)
      14. Nov 08 12:39:01 omv-pi CRON[10294]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
      15. Nov 08 12:39:01 omv-pi CRON[10297]: (root) CMD (for i in `pgrep "ftpd|nfsiod|smbd|afpd|cnid"` ; do ionice -c1 -p $i ;
      16. Nov 08 12:39:01 omv-pi CRON[10280]: pam_unix(cron:session): session closed for user root
      17. Nov 08 12:39:01 omv-pi CRON[10282]: pam_unix(cron:session): session closed for user root
      18. Nov 08 12:39:01 omv-pi CRON[10281]: pam_unix(cron:session): session closed for user root
      19. Nov 08 12:40:01 omv-pi CRON[10327]: pam_unix(cron:session): session opened for user root by (uid=0)
      20. Nov 08 12:40:01 omv-pi CRON[10331]: (root) CMD (for i in `pgrep "ftpd|nfsiod|smbd|afpd|cnid"` ; do ionice -c1 -p $i ;
      21. Nov 08 12:40:01 omv-pi CRON[10327]: pam_unix(cron:session): session closed for user root
      22. Nov 08 12:41:01 omv-pi CRON[10358]: pam_unix(cron:session): session opened for user root by (uid=0)
      23. Nov 08 12:41:01 omv-pi CRON[10362]: (root) CMD (for i in `pgrep "ftpd|nfsiod|smbd|afpd|cnid"` ; do ionice -c1 -p $i ;
      24. Nov 08 12:41:01 omv-pi CRON[10358]: pam_unix(cron:session): session closed for user root
      25. Nov 08 12:42:01 omv-pi CRON[10387]: pam_unix(cron:session): session opened for user root by (uid=0)
      26. Nov 08 12:42:01 omv-pi CRON[10391]: (root) CMD (for i in `pgrep "ftpd|nfsiod|smbd|afpd|cnid"` ; do ionice -c1 -p $i ;
      27. Nov 08 12:42:02 omv-pi CRON[10387]: pam_unix(cron:session): session closed for user root
      28. Nov 08 12:43:01 omv-pi CRON[10413]: pam_unix(cron:session): session opened for user root by (uid=0)
      29. Nov 08 12:43:01 omv-pi CRON[10417]: (root) CMD (for i in `pgrep "ftpd|nfsiod|smbd|afpd|cnid"` ; do ionice -c1 -p $i ;
      30. Nov 08 12:43:01 omv-pi CRON[10413]: pam_unix(cron:session): session closed for user root
      Display All
      Raid is not a backup! Would you go skydiving without a parachute?
    • Huberer wrote:

      There was an update. I saw it today and after the update docker didn't start anymore. Only by changing the fix, posted here something with ..UNIX:... and a reboot started docker and the containers again
      The *plugin* has not been updated. A new docker package (2018.09 over 2018.06) was released and it is causing this. I didn't know it was coming so there was no way to fix it. The plugin needs to be updated (no docker.socket unit) not just changing the systemd override file.
      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!
    • @geaves

      This is my output of "docker info" and I've changed to unix to. Maybe you made a typo because it shows 3 slashes ("/") after "unix:" Please check your correction again.

      Source Code

      1. root@OMV-HomeServer:~# docker info
      2. Containers: 7
      3. Running: 7
      4. Paused: 0
      5. Stopped: 0
      6. Images: 7
      7. Server Version: 18.09.0
      8. Storage Driver: overlay2
      9. Backing Filesystem: extfs
      10. Supports d_type: true
      11. Native Overlay Diff: true
      12. Logging Driver: json-file
      13. Cgroup Driver: cgroupfs
      14. Plugins:
      15. Volume: local
      16. Network: bridge host macvlan null overlay
      17. Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
      18. Swarm: inactive
      19. Runtimes: runc
      20. Default Runtime: runc
      21. Init Binary: docker-init
      22. containerd version: d6de12e2f362cb9dc49ad957911996d3de59b338
      23. runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
      24. init version: fec3683
      25. Security Options:
      26. apparmor
      27. seccomp
      28. Profile: default
      29. Kernel Version: 4.18.0-0.bpo.1-amd64
      30. Operating System: Debian GNU/Linux 9 (stretch)
      31. OSType: linux
      32. Architecture: x86_64
      33. CPUs: 8
      34. Total Memory: 15.46GiB
      35. Name: OMV-HomeServer
      36. ID: 7PHO:3CBS:WLG7:RTMC:7TFC:U6SZ:K6UX:JHNF:VBJL:B7WC:74JT:TPKG
      37. Docker Root Dir: /var/lib/docker
      38. Debug Mode (client): false
      39. Debug Mode (server): false
      40. Registry: https://index.docker.io/v1/
      41. Labels:
      42. Experimental: false
      43. Insecure Registries:
      44. 127.0.0.0/8
      45. Live Restore Enabled: false
      46. Product License: Community Engine
      47. WARNING: API is accessible on http://127.0.0.1:42005 without encryption.
      48. Access to the remote API is equivalent to root access on the host. Refer
      49. to the 'Docker daemon attack surface' section in the documentation for
      50. more information: https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
      51. WARNING: No swap limit support
      Display All
      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
    • geaves wrote:

      This is the output of docker info after the new docker ce install
      Yep, I can replicate it.
      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!