openmediavault-docker-gui Testing

nicjo814 · 13. November 2015

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

nicjo814 · 14. November 2015

Found a small typo in the init script (it worked anyway...). New release available:

openmediavault-docker-gui (0.2.20) testing

* Fix typo in init script

happyreacer · 15. November 2015

hi all,
can everybody help me for use a docker php-container in other docker container?

danieliod · 16. November 2015

I have a fresh insatall of omv 2.1.18 stoneburner | 64 bit | 3.16 backport kernel | omvextrasorg 2.8.
I have Docker Repo enabled and from some reason I don't see any Docker Plugins and specially not Docker-GUI.

What have I done wrong?

nicjo814 · 26. November 2015

Some time ago I mentioned "macvlan bridging" and how I needed this for some containers. I've now created a separate thread on the issue here: Docker public IP allocation "addon" for those interested in getting more of a VirtualBox/VMWare "bridged networking" feature to their Docker containers.

nicjo814 · 26. November 2015

Zitat von danieliod

I have a fresh insatall of omv 2.1.18 stoneburner | 64 bit | 3.16 backport kernel | omvextrasorg 2.8.
I have Docker Repo enabled and from some reason I don't see any Docker Plugins and specially not Docker-GUI.

What have I done wrong?

Late reply, but is the issue fixed?

Smurphy · 16. Dezember 2015

Still having the issues

Code

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

Code

root@nas:/etc/docker# ps auxw | grep docker
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.

Code

root@nas:/etc/docker# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination          


Chain FORWARD (policy ACCEPT)
target     prot opt source               destination          
DOCKER     all  --  0.0.0.0/0            0.0.0.0/0            
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            


Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination          


Chain DOCKER (1 references)
target     prot opt source               destination

Alles anzeigen

Anything I could check ?

nicjo814 · 16. Dezember 2015

3.2 is not backports kernel. Try to install it via omvextras plugin.

nicjo814 · 16. Dezember 2015

Also change the port the plugin uses in the settings page (to any other unused port) and re-save the changes.

happyreacer · 16. Dezember 2015

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

ryecoaaron · 16. Dezember 2015

There already is an 8.2 docker. link or here

Smurphy · 16. Dezember 2015

Zitat von nicjo814

3.2 is not backports kernel. Try to install it via omvextras plugin.

You're right. Somehow the system always used the latest kernel (this was from testing with btrfs)...
Rebooted - and apparently it works fine now. Error does not show up anymore. Thx.

happyreacer · 16. Dezember 2015

@ryecoaaron

Zitat

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.

nicjo814 · 16. Dezember 2015

Why not use bridge mode instead and map any ports you want?

happyreacer · 16. Dezember 2015

sorry, i don't know how i use britch mode corectly... can you help please

nicjo814 · 16. Dezember 2015

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

happyreacer · 17. Dezember 2015

@nicjo814 Thanks, it was very easy but, i will use port 443 and i have only port 80. Then i give a Custom Port 443 it don't work

happyreacer · 18. Dezember 2015

i cant use any container with https... anybody can help me?

subzero79 · 18. Dezember 2015

Zitat von happyreacer

anybody can help me?

What image?

happyreacer · 18. Dezember 2015

for example owncloud; pschmitt/owncloud; jchaney/owncloud
none one from the container work with https!?!? Port 80 work but 443 dont work.

Jetzt mitmachen!