Docker plugin - After the last update it does not start

    • OMV 4.x
    • Resolved
    • kyo wrote:

      I had this problem this morning too after the docker update.

      I removed the openmediavault-docker-gui 4.0.1 plugin using the GUI. Downloaded the 4.0.4 version @ryecoaaron posted earlier, and uploaded it from the Plugins page, installed the resulting plugin and everything went back to normal...

      Thanks a million!
      If I knew it was that simple :thumbsup:

      Everything's working normal again!


      Thanks,
      Frepke
    • Hello everyone,
      I am still having trouble after updating docker plugin.
      Right now I have tried uninstalling and reinstalling the plugin from the repo and modified the file:

      Source Code

      1. /etc/systemd/system/docker.service.d$ cat openmediavault.conf
      2. [Service]
      3. EnvironmentFile=-/etc/default/docker
      4. ExecStart=
      5. ExecStart=/usr/bin/dockerd -H unix:///var/run/docker.sock $DOCKER_OPTS \
      6. $OMVDOCKER_IMAGE_PATH

      Did I do anything wrong?

      I have tried rebooting and clearing cache (and other browser).
      Here below the current messages I have when I try to activate Docker:


      Source Code

      1. Errore #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}
      Display All
      Anybody has hints?
    • nick2k3 wrote:

      Did I do anything wrong?
      I haven't updated the plugin in the repo yet. Use the version I posted for testing - omv-extras.org/testing/openmediavault-docker-gui_4.1_all.deb
      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!
    • That worked for me. Thanks for the fix ryecoaaron. For others wondering step by step....download the deb file, upload it in the plugins tab, then go to the updates management tab and select the update. Clear browser cache and you should be good. All of my previous running containers fired right back up. Thanks again for the fix.
    • kmal808 wrote:

      That worked for me. Thanks for the fix ryecoaaron. For others wondering step by step....download the deb file, upload it in the plugins tab, then go to the updates management tab and select the update. Clear browser cache and you should be good. All of my previous running containers fired right back up. Thanks again for the fix.
      With that last comfirmation, I have put the update in the repo. So, people should be able to update from the Updates tab now (after clicking Check).
      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!
    • Thank you @ryecoaaron I have uploaded your plugin and installed it. I've also cleared cache but I still have this issue:

      Source Code

      1. Errore #0:
      2. OMV\AssertException: The property 'apiPort' does not exist in the model 'conf.service.docker'. in /usr/share/php/openmediavault/config/configobject.inc:71
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/config/configobject.inc(186): OMV\Config\ConfigObject->assertExists('apiPort')
      5. #1 /usr/share/php/openmediavault/config/configobject.inc(271): OMV\Config\ConfigObject->set('apiPort', '42005', false)
      6. #2 /usr/share/php/openmediavault/config/configobject.inc(233): OMV\Config\ConfigObject->setFlatAssoc(Array, false, false)
      7. #3 /usr/share/php/openmediavault/config/database.inc(90): OMV\Config\ConfigObject->setAssoc(Array, false)
      8. #4 /usr/share/openmediavault/engined/module/docker.inc(31): OMV\Config\Database->get('conf.service.do...')
      9. #5 /usr/share/openmediavault/engined/rpc/services.inc(56): OMVModuleDocker->getStatus()
      10. #6 [internal function]: OMVRpcServiceServices->getStatus(Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      12. #8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getStatus', Array, Array)
      13. #9 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Services', 'getStatus', Array, Array, 1)
      14. #10 {main}
      Display All

      the file /etc/systemd/system/docker.service.d/openmediavault.conf is still the same as my post above.
      Should I revert it to what it was before?

      EDIT: it works now!
      1) uninstall docker
      2) refresh plugin page
      3) install plugin
      4) clear cache
      5) re-configure docker base path
      6) everything works!

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

    • I still had errors after updating the plug-in. Docker refused to start. I had to manually remove the directory /run/docker.sock/.

      Source Code

      1. rm -r /run/docker.sock
      After that docker started with no problems.

      Source Code

      1. systemctl start docker.service
      Everything is fine now for me.
    • ryecoaaron wrote:

      nick2k3 wrote:

      Did I do anything wrong?
      I haven't updated the plugin in the repo yet. Use the version I posted for testing - omv-extras.org/testing/openmediavault-docker-gui_4.1_all.deb

      I'm guessing I should hold off a few days on updating this then? I just got OMV 4 up and running last weekend, as well as my ruTorrent image w/ over 600 torrents. I really do not want to have to re-check all these torrents again....

      Also, is there a way to back up docker images? I'm really in love with the current ruTorrent image that I'm running and want to back up that specific image in case things go wrong and need to be re-installed.
      Case: U-NAS NSC-810
      Motherboard: ASRock - C236 WSI Mini ITX
      CPU: Core i7-6700
      Memory: 32GB Crucial DDR4-2133
    • elastic wrote:

      I'm guessing I should hold off a few days on updating this then? I just got OMV 4 up and running last weekend, as well as my ruTorrent image w/ over 600 torrents. I really do not want to have to re-check all these torrents again....
      I uploaded the update (see post #70) and it is in the repo. People have had good luck with it. The only person who lost their dockers was someone who purged the plugin and docker packages.

      elastic wrote:

      Also, is there a way to back up docker images?
      Backing up your system should save it but should always be able to specify the specific version of the dockerfile to recreate 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!
    • Mine is borked too and I can't even remove docker properly. Even after uninstalling it via the GUI, I'm stuck with an entry under services and I can enter it and enable it, which throws an error message. How can I purge Docker properly?
      This is the first real problem I've had with OMV and it's one I have no idea how to even start to fix.
      Images
      • screencapture-192-168-1-250-2018-11-10-15_21_59.png

        233.35 kB, 1,919×1,972, viewed 29 times
      OMV 4.x, Gigabyte Z270N-WiFi, i7-6700K@3GHz, 16GB DDR4-3000, 4x 4TB Toshiba N300, 1x 60GB Corsair GT SSD (OS drive), 10Gbps Aquantia Ethernet
    • geaves wrote:

      TheLostSwede wrote:

      This is the first real problem I've had with OMV and it's one I have no idea how to even start to fix.
      I've had that when removing plugins, I usually start with apt-clean from omv-extras, if that doesn't sort it a clearing the browser cache is the next option.
      That did the trick, thanks
      OMV 4.x, Gigabyte Z270N-WiFi, i7-6700K@3GHz, 16GB DDR4-3000, 4x 4TB Toshiba N300, 1x 60GB Corsair GT SSD (OS drive), 10Gbps Aquantia Ethernet
    • ryecoaaron wrote:

      With that last comfirmation, I have put the update in the repo. So, people should be able to update from the Updates tab now (after clicking Check).

      @ryecoaaron Thanks for the fix! Today I installed all the docker updates including the new version of the omv-docker-plugin. Everything works as expected by the first try. :D

      Thanks and regards Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - tvos | android tv | libreelec | win10 | kodi krypton
      frontend hardware - appletv 4k | nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2
      -------------------------------------------
      backend software - debian | openmediavault | latest backport kernel | zfs raid-z2 | docker | emby | unifi | vdr | tvheadend | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------
    • @ryecoaaron First of all, thank you for all the support you give out. Your time is valuable and I recognise the time you put in here.

      I ran the update Sunday evening and also ran into an issue with Docker losing all images and running containers. I can the path I have set in the updated 4.1 plugin to be correct (/sharedfolders/docker) and the containers are still there. However, the images and containers are simply not showing.

      Docker is running with the following status

      Source Code

      1. service docker status
      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: active (running) since Mon 2018-11-12 18:35:08 GMT; 9min ago
      7. Docs: https://docs.docker.com
      8. Main PID: 870 (dockerd)
      9. Tasks: 17
      10. Memory: 110.6M
      11. CPU: 770ms
      12. CGroup: /system.slice/docker.service
      13. └─870 /usr/bin/dockerd -H unix:///var/run/docker.sock -g /srv/dev-disk-by-label-Media/docker
      14. Nov 12 18:35:04 storage dockerd[870]: time="2018-11-12T18:35:04.786453453Z" level=warning msg="Your kernel does not support cgroup rt period"
      15. Nov 12 18:35:04 storage dockerd[870]: time="2018-11-12T18:35:04.786489102Z" level=warning msg="Your kernel does not support cgroup rt runtime"
      16. Nov 12 18:35:04 storage dockerd[870]: time="2018-11-12T18:35:04.857555891Z" level=info msg="Loading containers: start."
      17. Nov 12 18:35:06 storage dockerd[870]: time="2018-11-12T18:35:06.316702063Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
      18. Nov 12 18:35:06 storage dockerd[870]: time="2018-11-12T18:35:06.424011956Z" level=info msg="Loading containers: done."
      19. Nov 12 18:35:08 storage dockerd[870]: time="2018-11-12T18:35:08.027687555Z" level=info msg="Docker daemon" commit=4d60db4 graphdriver(s)=vfs version=18.09.0
      20. Nov 12 18:35:08 storage dockerd[870]: time="2018-11-12T18:35:08.027874332Z" level=info msg="Daemon has completed initialization"
      21. Nov 12 18:35:08 storage dockerd[870]: time="2018-11-12T18:35:08.156007867Z" level=warning msg="Could not register builder git source: failed to find git binary: exec: \"git\": executable file not found in $PATH"
      22. Nov 12 18:35:08 storage dockerd[870]: time="2018-11-12T18:35:08.167349884Z" level=info msg="API listen on /var/run/docker.sock"
      23. Nov 12 18:35:08 storage systemd[1]: Started Docker Application Container Engine.
      Display All

      Versions are:

      Source Code

      1. dpkg -l | grep docker
      2. ii docker-ce 5:18.09.0~3-0~debian-stretch amd64 Docker: the open-source application container engine
      3. ii docker-ce-cli 5:18.09.0~3-0~debian-stretch amd64 Docker CLI: the open-source application container engine
      4. ii openmediavault-docker-gui 4.1 all OpenMediaVault plugin for Docker


      Not sure whats going on here but would be great if you could point out a path to resolution.

      Many thanks.
    • Walster wrote:

      Not sure whats going on here but would be great if you could point out a path to resolution.
      This really shouldn't happen unless you remove the plugin from the web interface (which would purge docker) and then re-install. Without seeing the output from the actual upgrade, it is hard to say what happened. What is the output of: cat /var/log/apt/term.log
      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