Docker GUI plugin now stable

So, do you recommend upgrading?
Is there a guide?

The guide is :
1. Reinstall everything.

Last night I tried upgrading a system clone in the spare disk. It failed miserably. So I reverted.

And I had another issue with docker while the plugin was offline. Suddenly my containers where not starting and then they disappeared. Without me doing anything, only rebooting. But in the end I managed to diagnose it.

I store the data from my containers in a ZFS array. Its mounted in the Z2 directory, and I refer it in my containers, for example: /Z2/docker-data/emby.
Well, since the docker plugin failed me, the docker service was starting before ZFS during boot. As the pool was not yet imported, there where no content in Z2, so docker decided to create the referenced folders. ZFS then attempted to mount the pool on Z2, but failed because the directory wasn't empty. So I missed the pool and containers because they couldn't boot.

I'll try to do a clean install on the spare disk, but we'll see how my arrays will be restored. Guys, that's not a nice situation. Now I'm thinking on the several installations I've done to some customers and where left alone at the datacenter.

Everytime I open Docker GUI in OMV2 I receive the following error.

Error: "couldn't connect to host" - Code: 7


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(145): OMVModuleDockerUtil::getImages('42005', 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}

I uninstalled and re-installed as well. Still happening.

I had some trouble trying to modify containers... the error "Error: "Failed to connect to localhost port 80: Connection refused" - Code: 7" appears when I try to SAVE the changes.

Can someone explain me what is happening?

Another thing: when MODIFY or COPY, the next screen (with container details) doesn't bring old stuff typed in "Extra args" field.

I use "--link XXXXXX" a lot... so the Extra args are a need for me, while the GUI doesn't support the --link

I just want to update my suggestion list based on what I saw in Docker for OMV3 (I had OMV2 at the time).

Zitat von anderbytes

### GENERAL ###

- [FEATURE] In Config tab, let us choose if "Run Image" screen comes with "Restart on system reboot", "Run container in privileged mode" and "Sync time with host" toggle each one ON or OFF by default. It's annyoing always having to robot-click some of those every time.

### IMAGES ###

- [FEATURE] Create a button near Images called "Check for Update", so we can query if a newer image is available. If so... give an option to Pull it. no typing...

- [FEATURE] Allow removing of those repo's and insertion of others. Makes that tab a lot more useful... (not possible, I guess)

- [FEATURE] Integrate more cool stuff! What about DockViz?? https://github.com/justone/dockviz

### NETWORKING ###

- [FEATURE] When running an image and Bridge is chosen, allow us to K.I.S.S. (Keep It Simple, Stupid) on ports. How? Pre-fill defaults exactly with port(s) seen in Dockerfile, and IP(s) pre-filled with host IP. If something is not as we please, we remove them and insert manually. 90% of the time we only copy the port number, without changing it.

- [FEATURE] When in Bridge. Pre-fill a suggested Host name with the word at right of "/" in image name (upper-case, ok?)

- [BUG] When chosen network type is "Host", you still ask for Host name, but it doesn't matter because it ends being replace by actual name from Docker Host. So... why ask i? Make it go away like the ports fields.

### CONTAINERS ###

- [FEATURE] When copying containers, please don't freeze "Docker image" field. Because when an image gets updated... that will be the field to save us from re-doing all configs at new image. Or maybe we want to create a beta environment of another stable one.... or go crazy and change Linux distro at next container. No limits here!

- [BUG] When copying containers, copied custom environment vars gets messed. I've already seen GIDs var switches with PIDs var and things like that... sometimes custom aren't brought at all to copied form.

### VOLUMES ###

- [FEATURE] Make it so that, when a "Host Path" is filled but nothing is filled at "Container Path", then just assume its equal to "Host Path". Would save a lot of time for some.

- [FEATURE] Today you make predicted Volumes (Ex: /config for some) available in a listbox. Well, about that...
---- Pre-create X editable lines, one for each predicted Container Path in Dockerfile, with that field pre-filled
---- We only can access predicted options by typing "/". Please create something like made in Exposed Ports list.
------- After the above done, don't make available already used options (no use in having 2 of any Container Path)

Alles anzeigen

I'll try to scavenge the source code and collaborate... don't know if I know enough web development for this.

EDIT: Problem solved by restarting docker in terminal, as was previously discussed in this thread.

Hi, I installed the plugin on my OMV 2.2.13 and activated it. I am new to docker. What do I have to do to be able to use handbrake or handbrake.cli with docker? I installed docker to be able to install handbrake without messing up the original OMV.

Do I have to do an Ubuntu installation as docker image/container? If so, how is it done over the GUI?

Does the '"Error: couldn't connect to host:" - Code 7' have relevance? It occures when I click on "Docker" under "Services" or when I click on the "search" bar inside the docker service GUI.

Thank you very much.

Error: "couldn't connect to host" - Code: 7
Error: "couldn't connect to host" - Code: 7
Error: "couldn't connect to host" - Code: 7
Error: "couldn't connect to host" - Code: 7
Fehler #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(145): OMVModuleDockerUtil::getImages('42005', 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}

I also experienced this "Error: "couldn't connect to host" - Code: 7" issue when I installed the plugin. For me the issue was that the kernel was too old. Looking in /var/log/docker.log there was written:

time="2016-12-22T13:46:18.074304788+01:00" level=fatal msg="Your Linux kernel version 3.2.0-4-amd64 is not supported for running docker. Please upgrade your kernel to 3.10.0 or newer."

So I am using Stone Burner 2.2.13 and the Kernel was 3.2.0-4. I installed the Backports-Kernel through OMV-extras. That one is 3.16.0-0 which seems to suffice. After rebooting with this kernel the plugin does not complain anymore and the docker service is running.

OMV 3 allows you to choose a newer kernel (4+), but Docker plugin crashes if I change to them.

Anyone is working into this?

I tested docker with 4.8 kernel, seems working well, what crash? any logs?

Zitat von luxflow

I tested docker with 4.8 kernel, seems works well, what crash? any logs?

I'll be posting it in the next few hours.

Zitat von luxflow

I tested docker with 4.8 kernel, seems working well, what crash? any logs?

I tracked down the issue to the following error:

root@SRV{/var/log}: systemctl -l status docker.service
docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled)
Drop-In: /etc/systemd/system/docker.service.d
+-openmediavault.conf
Active: failed (Result: exit-code) since Tue 2017-01-03 12:40:03 BRST; 6min ago
Docs: https://docs.docker.com
Process: 1183 ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS $OMVDOCKER_API $OMVDOCKER_IMAGE_PATH (code=exited, status=1/FAILURE)
Main PID: 1183 (code=exited, status=1/FAILURE)

Jan 03 12:40:02 SRV docker[1183]: time="2017-01-03T12:40:02.688499871-02:00" level=warning msg="[!] DON'T BIND ON ANY IP ADDRESS WITHOUT setting -tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING [!]"
Jan 03 12:40:02 SRV docker[1183]: time="2017-01-03T12:40:02.692333359-02:00" level=info msg="libcontainerd: new containerd process, pid: 1326"
Jan 03 12:40:03 SRV docker[1183]: time="2017-01-03T12:40:03.712906769-02:00" level=error msg="[graphdriver] prior storage driver \"aufs\" failed: driver not supported"
Jan 03 12:40:03 SRV docker[1183]: time="2017-01-03T12:40:03.712961967-02:00" level=fatal msg="Error starting daemon: error initializing graphdriver: driver not supported"
Jan 03 12:40:03 SRV systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Jan 03 12:40:03 SRV systemd[1]: Failed to start Docker Application Container Engine.
Jan 03 12:40:03 SRV systemd[1]: Unit docker.service entered failed state.

It seems that Kernels 4+ don't like AUFS

Zitat von ryecoaaron

That is why we removed aufs from the unionfilesystems plugin. It isn't in the backports kernel and won't be in future versions of Debian. You need to switch to use devicemapper - Docker GUI plugin now stable

Damn!

So I'll have to rebuild all my containers?

I have heard well of OverLayFS... guess I'll try that one