Docker plugin - After the last update it does not start

    • OMV 4.x
    • Resolved
    • Thanks for the help, @ryecoaaron, that seems to have done the trick! No more errors when popping into the Docker service. I really appreciate your help!

      I'm relatively new to Linux, and am really curious what that process did. From what i could gather, it looks like the touch command tells the OS to update the file's "last updated" metadata to that moment.

      Then the apt-get -f install seems to look for broken dependencies and tries to fix them. Interestingly, the output of that command showed that nothing was changed. Yet something definitely fixed the problem.

      If it's not too much trouble, I'd love to learn the mechanics behind what that did.

      As far as the 'yuck' in response to it being an RPi, is that because it's so underpowered that it makes for a less-than-optimal NAS experience? If so, I totally get it. It does make for a fun, inexpensive platform to learn on, though. :)

      Thanks again!
    • Peekay wrote:

      it looks like the touch command tells the OS to update the file's "last updated" metadata to that moment.
      It does that as well as create the file if it doesn't exist.

      Peekay wrote:

      Then the apt-get -f install seems to look for broken dependencies and tries to fix them. Interestingly, the output of that command showed that nothing was changed. Yet something definitely fixed the problem.
      It may not have had to fix anything but it doesn't hurt to run. It could've started the service as well.

      Peekay wrote:

      As far as the 'yuck' in response to it being an RPi, is that because it's so underpowered that it makes for a less-than-optimal NAS experience? If so, I totally get it. It does make for a fun, inexpensive platform to learn on, though.
      It is terrible NAS, yes. The problem is that the RPi image is using armbian but isn't really supported and there a few issues when filling in the gaps with the raspberrypi.org repo. I would prefer people purchase a rock64 (cheaper and much faster than an RPi) or rockpro64 (for a bit more) instead :) I have a rockpro64 and it is very stable.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • justtim wrote:

      Are they ok to install now, or should I wait for a newer version?
      There is nothing to fix with the plugin. The problem with the RPi is with the docker package/repos which we don't maintain. Backup your system and try it. I won't guarantee anything with the RPi.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • justtim wrote:

      Did some further research and it looks like its best to wait a bit longer. For the RPi owners stumbling on this tread: github.com/moby/moby/issues/38175
      That issue isn't relevant. 18.06 is being installed and works. It is just touchy about getting to that point.

      Display Spoiler

      root@raspberrypi:~# dpkg -l | grep dock
      ii docker-ce 18.06.1~ce~3-0~debian armhf Docker: the open-source application container engine
      root@raspberrypi:~# systemctl status docker
      ● docker.service - Docker Application Container Engine
      Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
      Active: active (running) since Wed 2018-10-24 13:54:41 UTC; 1 months 3 days ago
      Docs: docs.docker.com
      Main PID: 938 (dockerd)
      CPU: 12h 14min 20.308s
      CGroup: /system.slice/docker.service
      ├─ 938 /usr/bin/dockerd -H fd://
      └─1047 docker-containerd --config /var/run/docker/containerd/containerd.toml
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • justtim wrote:

      I am on 18.06. People start having issues when updating to 18.09 on their ARM based systems which is exactly the update waiting to be installed on my system.
      You are correct abou 18.06. I forgot I reverted my RPi to try and figure this out AND mixed up the version number even though I just locked the plugin to use 18.09. My bad. But my point still stands. 18.09 is working on my RPi:

      Display Spoiler

      root@raspberrypi:~# systemctl status containerd
      ● containerd.service - containerd container runtime
      Loaded: loaded (/lib/systemd/system/containerd.service; enabled; vendor preset: enabled)
      Active: active (running) since Tue 2018-11-27 16:13:49 UTC; 2min 31s ago
      Docs: containerd.io
      Process: 779 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
      Main PID: 793 (containerd)
      CPU: 621ms
      CGroup: /system.slice/containerd.service
      └─793 /usr/bin/containerd

      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.782970465Z" level=info msg="loading plugin "io.co
      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.783140465Z" level=info msg="loading plugin "io.co
      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.783297757Z" level=info msg="loading plugin "io.co
      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.783824684Z" level=info msg="loading plugin "io.co
      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.802490204Z" level=info msg="loading plugin "io.co
      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.802830829Z" level=info msg="loading plugin "io.co
      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.803152809Z" level=info msg="loading plugin "io.co
      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.803509892Z" level=info msg="loading plugin "io.co
      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.807068486Z" level=info msg=serving... address="/r
      Nov 27 16:13:51 raspberrypi containerd[793]: time="2018-11-27T16:13:51.809692236Z" level=info msg="containerd successful
      root@raspberrypi:~# systemctl status docker
      ● docker.service - Docker Application Container Engine
      Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
      Active: active (running) since Tue 2018-11-27 16:14:04 UTC; 2min 23s ago
      Docs: docs.docker.com
      Main PID: 968 (dockerd)
      CPU: 3.035s
      CGroup: /system.slice/docker.service
      └─968 /usr/bin/dockerd -H unix://

      Nov 27 16:14:00 raspberrypi dockerd[968]: time="2018-11-27T16:14:00.824303495Z" level=warning msg="Your kernel does not
      Nov 27 16:14:00 raspberrypi dockerd[968]: time="2018-11-27T16:14:00.824475369Z" level=warning msg="Your kernel does not
      Nov 27 16:14:00 raspberrypi dockerd[968]: time="2018-11-27T16:14:00.826461090Z" level=warning msg="mountpoint for pids n
      Nov 27 16:14:00 raspberrypi dockerd[968]: time="2018-11-27T16:14:00.829787431Z" level=info msg="Loading containers: star
      Nov 27 16:14:03 raspberrypi dockerd[968]: time="2018-11-27T16:14:03.180717334Z" level=info msg="Default bridge (docker0)
      Nov 27 16:14:03 raspberrypi dockerd[968]: time="2018-11-27T16:14:03.981983552Z" level=info msg="Loading containers: done
      Nov 27 16:14:04 raspberrypi dockerd[968]: time="2018-11-27T16:14:04.703150866Z" level=info msg="Docker daemon" commit=4d
      Nov 27 16:14:04 raspberrypi dockerd[968]: time="2018-11-27T16:14:04.711559739Z" level=info msg="Daemon has completed ini
      Nov 27 16:14:04 raspberrypi dockerd[968]: time="2018-11-27T16:14:04.912745248Z" level=info msg="API listen on /var/run/d
      Nov 27 16:14:04 raspberrypi systemd[1]: Started Docker Application Container Engine.
      root@raspberrypi:~# dpkg -l | grep docker
      ii docker-ce 5:18.09.0~3-0~debian-stretch armhf Docker: the open-source application container engine
      ii docker-ce-cli 5:18.09.0~3-0~debian-stretch armhf Docker CLI: the open-source application container engine
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • @ryecoarron:
      Since you're looking in on this thread, what do you make of the following? I'm not running containers yet so I don't know if there's a functional impact. This shows up in the syslog as well.
      ___________________________________________________________________________
      root@OMV-INTEL:~# systemctl status docker
      ● docker.service - Docker Application Container Engine
      Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
      Drop-In: /etc/systemd/system/docker.service.d
      └─openmediavault.conf
      Active: active (running) since Tue 2018-11-27 03:25:25 EST; 8h ago
      Docs: docs.docker.com
      Main PID: 1059 (dockerd)
      Tasks: 21
      Memory: 42.9M
      CPU: 13.767s
      CGroup: /system.slice/docker.service
      └─1059 /usr/bin/dockerd -H unix:///var/run/docker.sock


      Nov 27 03:25:24 OMV-INTEL dockerd[1059]: time="2018-11-27T03:25:24.372067775-05:00" level=warning msg="Your kernel does not support swap memory limit"
      Nov 27 03:25:24 OMV-INTEL dockerd[1059]: time="2018-11-27T03:25:24.372150197-05:00" level=warning msg="Your kernel does not support cgroup rt period"
      Nov 27 03:25:24 OMV-INTEL dockerd[1059]: time="2018-11-27T03:25:24.372172412-05:00" level=warning msg="Your kernel does not support cgroup rt runtime"
      /-------------------/

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 4.1.17, ThinkServer TS140, 12GB ECC, 16GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.17, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • ryecoaaron wrote:

      What kernel version?
      Sorry, I should know better.

      Debian GNU/Linux, with Linux 4.18.0-0.bpo.1-amd64

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 4.1.17, ThinkServer TS140, 12GB ECC, 16GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.17, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • ryecoaaron wrote:

      You are correct abou 18.06. I forgot I reverted my RPi to try and figure this out AND mixed up the version number even though I just locked the plugin to use 18.09. My bad. But my point still stands. 18.09 is working on my RPi
      Allright. I decided to make a full backup and take my chances. Guess what, everything is fine and Docker is running stable on 18.09 :thumbsup: .
      Out of curiosity, what CPU model do you have in your RPi? Mine is a ARMv7 Processor rev 5 (v7l). Looking at the GitHub issue, the problem seems to be limited to the ARMv6 CPU models in older RPis.

      flmaxey wrote:

      Nov 27 03:25:24 OMV-INTEL dockerd[1059]: time="2018-11-27T03:25:24.372150197-05:00" level=warning msg="Your kernel does not support cgroup rt period"
      Nov 27 03:25:24 OMV-INTEL dockerd[1059]: time="2018-11-27T03:25:24.372172412-05:00" level=warning msg="Your kernel does not support cgroup rt runtime"
      I get these 2 as well. Containers are fine. Don't know if it has always been like that, or since the latest update.
    • justtim wrote:

      Out of curiosity, what CPU model do you have in your RPi?
      This RPi is an RPi2 which is v7.

      justtim wrote:

      Looking at the GitHub issue, the problem seems to be limited to the ARMv6 CPU models in older RPis.
      That would make sense. The RPi1 is v6 and almost an armel cpu. Not worth running docker on. OMV doesn't really work on them anymore anyway.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • flmaxey wrote:

      Debian GNU/Linux, with Linux 4.18.0-0.bpo.1-amd64
      I'm not seeing those but I will look a bit more. Maybe it has to do with an older CPU?
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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:

      Maybe it has to do with an older CPU?
      Maybe,, the CPU is definitely older so some of the standard features supported in later CPU's wouldn't be there. Don't you have a box running Xeon E5620's?
      The issue couldn't (well shouldn't) be kernel related. We know the latest kernels fully support Docker. Maybe I'll config up a Docker just to see if there's any effect, or if syslog gets a ton of entries.

      Since I'm thinking about rebuilding anyway, maybe I'll back off to 4.14 to see what happens, then give the Promox kernel a try.


      geaves wrote:

      Or the older user :D :D :D :D :D

      Hey brother,, I think you're older than I am. Much older, as in many months older. :rolleyes:

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 4.1.17, ThinkServer TS140, 12GB ECC, 16GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.17, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • flmaxey wrote:

      Don't you have a box running Xeon E5620's?
      Yes but it isn't plugged in.

      flmaxey wrote:

      The issue couldn't (well shouldn't) be kernel related. We know the latest kernels fully support Docker. Maybe I'll config up a Docker just to see if there's any effect, or if syslog gets a ton of entries
      The two cgroup rt warnings have to do with not using the realtime kernel. I have these and there is nothing to worry about. I don't have the other warning but this seems to be just a warning from what I can find. Unless you are having a problem, I wouldn't worry about it. There are fixes on the net but I haven't used any of them.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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:

      I don't have the other warning but this seems to be just a warning from what I can find. Unless you are having a problem, I wouldn't worry about it. There are fixes on the net but I haven't used any of them.
      I kind of suspected it wasn't anything to worry about. I'll be testing Docker, to see if there's an issue, before rebuilding.

      Thanks for taking a look.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 4.1.17, ThinkServer TS140, 12GB ECC, 16GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.17, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • Apologies for yet another input into here, but I decided to remove the plugin and reinstall as I was unable to resolve error I was seeing.

      Removed all the containers, removed the plugin, ran apt clean, reinstalled plugin -> error docker not found
      1. So disabled Docker CE repo, apt clean, re enabled Docker CE repo
      2. Installed plugin -> docker not found

      I have completed the above 1 & 2 twice and still the same, but took some screen shots




      I'm not sure what to try next?

      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 Wed 2018-11-28 11:27:29 GMT; 13s ago
      7. Docs: https://docs.docker.com
      8. Process: 18814 ExecStart=/usr/bin/dockerd -H unix:///var/run/docker.sock $DOCKER_OPTS $OMVDOCKER_IMAGE_PATH (code=exited, stat
      9. Main PID: 18814 (code=exited, status=203/EXEC)
      10. CPU: 1ms
      11. Nov 28 11:27:27 homenas systemd[1]: docker.service: Main process exited, code=exited, status=203/EXEC
      12. Nov 28 11:27:27 homenas systemd[1]: Failed to start Docker Application Container Engine.
      13. Nov 28 11:27:27 homenas systemd[1]: docker.service: Unit entered failed state.
      14. Nov 28 11:27:27 homenas systemd[1]: docker.service: Failed with result 'exit-code'.
      15. Nov 28 11:27:29 homenas systemd[1]: docker.service: Service hold-off time over, scheduling restart.
      16. Nov 28 11:27:29 homenas systemd[1]: Stopped Docker Application Container Engine.
      17. Nov 28 11:27:29 homenas systemd[1]: docker.service: Start request repeated too quickly.
      18. Nov 28 11:27:29 homenas systemd[1]: Failed to start Docker Application Container Engine.
      19. Nov 28 11:27:29 homenas systemd[1]: docker.service: Unit entered failed state.
      20. Nov 28 11:27:29 homenas systemd[1]: docker.service: Failed with result 'exit-code'.
      Display All


      Source Code

      1. journalctl -xe
      2. Nov 28 11:28:42 homenas systemd[1]: docker.service: Main process exited, code=exited, status=203/EXEC
      3. Nov 28 11:28:42 homenas systemd[1]: Failed to start Docker Application Container Engine.
      4. -- Subject: Unit docker.service has failed
      5. -- Defined-By: systemd
      6. -- Support: https://www.debian.org/support
      7. --
      8. -- Unit docker.service has failed.
      9. --
      10. -- The result is failed.
      11. Nov 28 11:28:42 homenas systemd[1]: docker.service: Unit entered failed state.
      12. Nov 28 11:28:42 homenas systemd[1]: docker.service: Failed with result 'exit-code'.
      13. Nov 28 11:28:44 homenas systemd[1]: docker.service: Service hold-off time over, scheduling restart.
      14. Nov 28 11:28:44 homenas systemd[1]: Stopped Docker Application Container Engine.
      15. -- Subject: Unit docker.service has finished shutting down
      16. -- Defined-By: systemd
      17. -- Support: https://www.debian.org/support
      18. --
      19. -- Unit docker.service has finished shutting down.
      20. Nov 28 11:28:44 homenas systemd[1]: docker.service: Start request repeated too quickly.
      21. Nov 28 11:28:44 homenas systemd[1]: Failed to start Docker Application Container Engine.
      22. -- Subject: Unit docker.service has failed
      23. -- Defined-By: systemd
      24. -- Support: https://www.debian.org/support
      25. --
      26. -- Unit docker.service has failed.
      27. --
      28. -- The result is failed.
      29. Nov 28 11:28:44 homenas systemd[1]: docker.service: Unit entered failed state.
      30. Nov 28 11:28:44 homenas systemd[1]: docker.service: Failed with result 'exit-code'.
      Display All
      Raid is not a backup! Would you go skydiving without a parachute?