openmediavault-docker-gui Testing

    • OMV 2.x

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

    • openmediavault-docker-gui Testing

      Do they have https enabled? Otherwise I guess you need to configure https access manually within the container with some kind of self-signed certificate. Have you set up https manually before, let's say for secure access to an Apache web server? If not, there is a lot of information on this topic if you Google a bit...
    • I've used comes with a certificate included inside but you can change it i guess says the hub repo info

      docker run --name oc -p 7000:80 -p 7001:443 -d l3iggs/owncloud…fb9b9eb87b0fc0552671c2c19
      • Screen Shot 2015-12-18 at 7.51.23 PM.png

        60.14 kB, 1,032×285, viewed 410 times
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10 broadcast channel
      openmediavault discord server
    • I've been quite busy with converting the plugin to be OMV 3.x compatible and now I feel like it's ready for some beta testing. This requires a VM where to install OMV 3.x, which is still in beta and thus probably still has some issues. For anyone interested in helping out and testing the latest features of the Docker plugin this is how to do it (please note that package installation from web ui is currently broken in OMV3.x, that's why cli stuff is required):
      1. Download OMV 3.0 from here (…ediavault_3.0.2-amd64.iso) and install in a VM
      2. After install is finished enter cli and do: apt-get update && apt-get upgrade
      3. Download omvextrasorg from here (…mvextrasorg_3.0.5_all.deb) and upload via plugins web gui page
      4. Enter cli and do: apt-get update && apt-get install openmediavault-omvextrasorg
      5. Enable the Docker repo in omvextras, save and apply
      6. Enter cli and do: apt-get update && apt-get install openmediavault-docker-gui
      Here is the changelog for the 3.x branch of the plugin:
      openmediavault-docker-gui (3.0.3) stable; urgency=medium

      * Minor tweaks to the repo tab
      * Add logos to the docker images
      * Add php5-imagick dependancy
      * Make it possible to edit port forwarding rows
      * Make it possible to edit environment variable rows
      * Make it possible to edit bind mount rows
      * Make it possible to edit volumes from rows
      * Add tooltips to buttons
      * Add info button to repo tab entries
      * Reload repo tab when a new image is pulled
      * Make repo tab hidden if plugin is not enabled

      openmediavault-docker-gui (3.0.2) stable; urgency=medium

      * Add r/o mode to bind mounts
      * Stability fixes to Docker service restart
      * Add images to the repo tab
      * Usability improvements on the repo tab

      openmediavault-docker-gui (3.0.1) stable; urgency=medium

      * Fix postrm script to use systemd
      * Add fixes to ensure proper upgrade from 0.2.x plugin branch

      openmediavault-docker-gui (3.0.0) stable; urgency=low

      * Make plugin OMV 3.x compatible
      * Add support for network port types (tcp/udp)
      * Rename "Docker repo" to "Docker images repo"
      * Make time sync with host default when running container
      * Make restart always policy default when running container

      I think the plugin has improved quite a lot from the 0.2.x branch (but I might be a bit biased :) ). Also a big thanks to the guys at for helping out with repo images and general improvement ideas.
    • Here is another new feature that I think will be of quite good use. I've added the possibility to "modify" the settings on a running container, making it possible to quicky change ports, bind-mounts etc without having to copy the container. This new feature comes with a BIG warning... It's implemented by saving all "old" settings, removing the existing container, (tries to) starting up a new container with the "modified" settings. If this last step fails, the plugin will create a new container with the "old" settings instead.

      There are two things that can go wrong here which I want to point out before you use this function.
      1. All non-persistent data within the container will be deleted. That is all data that is local to the container itself and is not-bind-mounted from the host or otherwise located outside of the running container.
      2. There is no guarantee that the plugin will be successful when trying to use the "old" settings to re-create the container if the "new" settings failed. This could result in loss of the container itself and all associated settings.
      ​Now I REALLY would appreciate your help with testing this function out as soon as it's included in the plugin (soon) and also feedback on how it's working out, if it fails etc.

      This post is also referenced via a warning displayed in the plugin when a user tries to modify a running container.
    • Regarding the sluggish behaviour of the container panel
      This is a log using using omv-engined -d -f

      Notice here that i am not using the shared folder volume selector, neither the default location, i placed manually symlink from /var/lib/docker to /media/<uuid>/docker where i store everything

      I also use btrfs as fs driver.
      Hope it helps, is really slow the panel, sometimes it doesn't even come up with nothing.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10 broadcast channel
      openmediavault discord server
    • I *think* I managed to improve the performance based on the debug log you provided. There were a number of warnings there that I hadn't noticed before, which might have had a bad impact on the overall performance. The fixes are included in 3.0.5 which is available on Bintray. With 12 containers running it took approx 2 seconds to load the container grid (when the overall cpu load was at an ok level).
    • Hi,

      Im getting the following error when i click on the docker icon within the OMV dashboard.

      Source Code

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

      Does anyone know what is causing this?

    • I did a fresh OMV 2.0 install last night. I added the dockerplug-in via OMV-extras. I selected two images to try and both fail in the same manner images were couchpotato and sickrage. sickrage info doesn't list anything so I just selected the image and clicked run image then gave it a name and then clicked save Both fail with the following error.

      Source Code

      1. ​Error #0:
      2. exception 'OMVModuleDockerException' with message 'bcf23c4d9f189f02f08998fffd70985c9edaea9447a7d202a0a7f6215234df1d
      3. docker: Error response from daemon: rpc error: code = 2 desc = "shim error: invalid argument".' in /usr/share/omvdocker/Utils.php:517
      4. Stack trace:
      5. #0 /usr/share/openmediavault/engined/rpc/ OMVModuleDockerUtil::exec('docker run -d -...', Array, 125)
      6. #1 [internal function]: OMVRpcServiceDocker->runContainer(Array, Array)
      7. #2 /usr/share/php/openmediavault/ call_user_func_array(Array, Array)
      8. #3 /usr/share/php/openmediavault/ OMVRpcServiceAbstract->callMethod('runContainer', Array, Array)
      9. #4 /usr/sbin/omv-engined(500): OMVRpc::exec('Docker', 'runContainer', Array, Array, 1)
      10. #5 {main}

      Googling got me to this page which suggests it's a kernel 3.2 issue and that came up after docker 1.11 came out. sure enough

      Source Code

      1. ​uname -a
      2. Linux openmediavault 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64 GNU/Linux


      Source Code

      1. ​docker --version
      2. Docker version 1.11.2, build b9f10c9

      so the docker thread says that they don't support 3.2 and update. Does this happen for everyone else on OMV 2.0? Any suggestions?
    • jamief wrote:

      Does this happen for everyone else on OMV 2.0? Any suggestions?

      I always though docker was only for bpo kernel, reports later came from forum users that up to certain version of docker-engine the default kernel of debian wheezy worked. Now i remember the the docker documentation was always pointing to bpo kernel.
      What i figure out later it is the requirement was elevated because of some serious bugs in the wheezy stock kernel in regards of using docker.

      Bottom line, you need wheezy backport kernel to make it work with docker-engine
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10 broadcast channel
      openmediavault discord server
    • I'm try to map my host mysql to docker, but I can't get it connect.
      I've created the database/user for this container before start the installation.

      Is this the correct path?

      Host path:

      Container path:
      • Pydio container settings_1.PNG

        48.77 kB, 601×704, viewed 379 times
      OMV v4.0
      Asus Z97-A/3.1; i3-4370
      32GB RAM Corsair Vengeance Pro
      4x3TB RAID10