openmediavault-docker-gui Testing

    • OMV 2.x

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

    • Well I just have to release a new testing version today (since I want the new functionality myself :) ) This new release changes how the plugin handles remounting the OMV share when relocating the Docker runtime path. Now remounting is handled by a an insserv script in /etc/init.d which makes it possible to do the actual remounting BEFORE the docker service starts. Also it's thus possible to write your own insserv scripts depending on the docker service (which is what I want to do...). So please help me test this new release.

      openmediavault-docker-gui (0.2.19) testing
      * Improved solution for remounting Docker runtime directory
      noexec at reboot
    • Still having the issues

      Source Code

      1. Error #0:
      2. exception 'OMVModuleDockerException' with message 'Error: "couldn't connect to host" - Code: 7' in /usr/share/omvdocker/Utils.php:63
      3. Stack trace:
      4. #0 /usr/share/omvdocker/Utils.php(125): OMVModuleDockerUtil::doApiCall('http://localhos...')
      5. #1 /usr/share/openmediavault/engined/rpc/docker.inc(143): OMVModuleDockerUtil::getImages('41005', true)
      6. #2 [internal function]: OMVRpcServiceDocker->getImages(Array, Array)
      7. #3 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      8. #4 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getImages', Array, Array)
      9. #5 /usr/sbin/omv-engined(500): OMVRpc::exec('Docker', 'getImages', Array, Array, 1)
      10. #6 {main}


      Tried all that was proposed in this thread already to this issue.
      anyone has a clue ?

      Running latest omv-all (Stable ones), backported kernel (3.2.0-4).
      Docker process seems to be running.

      Source Code

      1. root@nas:/etc/docker# ps auxw | grep docker
      2. root 8603 0.0 0.1 112388 21528 ? Sl 11:58 0:02 /usr/bin/docker daemon -p /var/run/docker.pid


      FYI - I am not running iptables (NAS is for internal use only), however it seems the docker process has enabled some filter rules.

      Source Code

      1. root@nas:/etc/docker# iptables -L -n
      2. Chain INPUT (policy ACCEPT)
      3. target prot opt source destination
      4. Chain FORWARD (policy ACCEPT)
      5. target prot opt source destination
      6. DOCKER all -- 0.0.0.0/0 0.0.0.0/0
      7. ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
      8. ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
      9. ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
      10. Chain OUTPUT (policy ACCEPT)
      11. target prot opt source destination
      12. Chain DOCKER (1 references)
      13. target prot opt source destination
      Display All


      Anything I could check ?
      Linux user since 1992 ...
    • Please can make everyone a Docker container for owncloud 8.2?
      With http port mybe 50080 and https port mybe 50443 or host/owncloud
      and can we add it to the repo

      I think it helps to close many therds on the forum ;)
      omv 3.0.88 | 64 bit | omvextrasorg 3.4.26 | kernel 4.9
      used plugins: nginx | mysql | docker-gui | flashmemory |rsnapshot | antivirus | apt tool | letsEncrypt | fail2ban for omv-webgui/Nextcloud/emby
      used other: netxtcloud | logitechmediaserver | emby
    • @ryecoaaron
      There already is an 8.2 docker. link or here

      i know, but the container have no https on default and i don't know how can i change the ports on the webgui when i use it in host option.
      omv 3.0.88 | 64 bit | omvextrasorg 3.4.26 | kernel 4.9
      used plugins: nginx | mysql | docker-gui | flashmemory |rsnapshot | antivirus | apt tool | letsEncrypt | fail2ban for omv-webgui/Nextcloud/emby
      used other: netxtcloud | logitechmediaserver | emby
    • In the plugin, specify bridged mode networking for your container. Then for each network port of the container (listed in the "Exposed port" dropdown in the "port forwarding" fieldset), specify a non-used port on the host in the "Host port" field. An example: The container you want to run listens on port 80 for http web connections, then select a port (like 9080) and specify it in the "Host port" field and select port 80 in the "Exposed port" dropdown. Finally click the "plus" button to the right to "commit" your selection. Now you will be able to reach the web interface of your container on http://<ip of your host>:9080
    • for example owncloud; pschmitt/owncloud; jchaney/owncloud
      none one from the container work with https!?!? Port 80 work but 443 dont work.
      omv 3.0.88 | 64 bit | omvextrasorg 3.4.26 | kernel 4.9
      used plugins: nginx | mysql | docker-gui | flashmemory |rsnapshot | antivirus | apt tool | letsEncrypt | fail2ban for omv-webgui/Nextcloud/emby
      used other: netxtcloud | logitechmediaserver | emby