Docker error

    • OMV 4.x
    • Docker error

      I had docker working perfectly with plex etc- no dramas.

      I've got luks encryption so followed some guides using dropbear to remote unlock- that is working now too.

      But now docker isn't working- I can't quite work out the connection between the two- this is the error

      Source Code

      1. Error #0:
      2. OMVModuleDockerException: Error: "Operation timed out after 30001 milliseconds with 0 bytes received" - Code: 28 in /usr/share/omvdocker/Utils.php:73
      3. Stack trace:
      4. #0 /usr/share/omvdocker/Utils.php(196): OMVModuleDockerUtil::doApiCall('http://localhos...')
      5. #1 /usr/share/openmediavault/engined/rpc/docker.inc(211): OMVModuleDockerUtil::getImageList(42005, true)
      6. #2 [internal function]: OMVRpcServiceDocker->getImages(Array, Array)
      7. #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      8. #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getImages', Array, Array)
      9. #5 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'getImages', Array, Array, 1)
      10. #6 {main}

      Along with a 'Bad Gateway' error. I had set a static IP in initramfs.conf- I deleted that and put a manual IP in my router (so I could still SSH in to unlock on a static IP), no difference.

      Help please- thanks.
    • Update- got impatient so though I'd just reinstall.

      Bad idea- incomplete uninstall via OMV, locked apt-get, manual reboots and apt remove are also unsuccessful.

      Something bad seems to have happened- this is the error on reinstall-

      Source Code

      1. Job for docker.service failed because the control process exited with error code.
      2. See "systemctl status docker.service" and "journalctl -xe" for details.
      3. invoke-rc.d: initscript docker, action "start" failed.
      4. * docker.service - Docker Application Container Engine
      5. Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
      6. Active: activating (auto-restart) (Result: exit-code) since Sat 2018-06-09 23:50:59 AWST; 11ms ago
      7. Docs: https://docs.docker.com
      8. Process: 3563 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
      9. Main PID: 3563 (code=exited, status=1/FAILURE)
      10. CPU: 51ms
      11. Jun 09 23:50:59 n54ldebian9 systemd[1]: docker.service: Main process exited,…URE
      12. Jun 09 23:50:59 n54ldebian9 systemd[1]: Failed to start Docker Application C…ne.
      13. Jun 09 23:50:59 n54ldebian9 systemd[1]: docker.service: Unit entered failed …te.
      14. Jun 09 23:50:59 n54ldebian9 systemd[1]: docker.service: Failed with result '…e'.
      15. Hint: Some lines were ellipsized, use -l to show in full.
      16. dpkg: error processing package docker-ce (--configure):
      17. subprocess installed post-installation script returned error exit status 1
      18. dpkg: dependency problems prevent configuration of openmediavault-docker-gui:
      19. openmediavault-docker-gui depends on docker-ce; however:
      20. Package docker-ce is not configured yet.
      21. dpkg: error processing package openmediavault-docker-gui (--configure):
      22. dependency problems - leaving unconfigured
      23. Errors were encountered while processing:
      24. docker-ce
      25. openmediavault-docker-gui
      Display All

      The post was edited 1 time, last by johnnyb ().

    • Sounds like docker is starting before you unlock the filesystem. Try adding a systemd override file that makes the docker service wait for the local filesystem.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

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

      Sounds like docker is starting before you unlock the filesystem. Try adding a systemd override file that makes the docker service wait for the local filesystem.
      Thanks for the post ryecoaaron, have you got a link to help me through creating such a file?

      Also- is there any significance to these error messages-

      Your kernel does not support swap memory limit
      Your kernel does not support cgroup rt period
      Your kernel does not support cgroup rt runtime
    • johnnyb wrote:

      have you got a link to help me through creating such a file?
      No but it would look something like:
      sudo nano /etc/systemd/system/docker.service.d/override.conf
      add these lines:
      [Unit]
      After=local-fs.target
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

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

      No luck unfortunately, same errors.
      That was just a guess. You could try other targets like multi-user.target

      johnnyb wrote:

      Trying to uninstall the plugin via GUI again just seems to break things.
      Errors? I would remove it from the command line for better output.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

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

      That was just a guess. You could try other targets like multi-user.target

      Thanks for spending time on this ryecoaaron- appreciate it.

      I reinstalled with GUI after going through the motions manually removing and cleaning up (sorry didn't record the errors).

      Docker survives reboots when I have no containers loaded. As soon as I run an image, it doesn't survive a reboot.
    • Update from me- think I sorted it.

      Not surprisingly it was probably my error all along in the end. With PUID/PGID I had created new users for the specific containers (plex, sonarr etc) under the group 'media', in an attempt to separate out users.

      I changed this to my default user and group and have rebooted after loading each container- docker survives.

      Thanks again ryecoaaron.
    • Users Online 1

      1 Guest