I have cleared the browser cache repeatedly. No change.
Docker GUI plugin now stable
-
- OMV 2.x
- nicjo814
-
-
Well you can open dev console to check the js source has the new directive.
-
Well you can open dev console to check the js source has the new directive.
Huh?
-
You said you applied the patch manually. Have you check the js source files that your patch was applied?
Or did you build the source as a package?
-
Hoping for some advice - again
Got docker up and running on Odroid HC2 running OMV 4x. Now i need to get Emby up and running. Found this docker img: embyserver_arm32v7
but just get errors when running it:Code
Alles anzeigenError #0: OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; docker run -d --restart=always -v /etc/localtime:/etc/localtime:ro --net=host -e PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" -e LANG="en_US.UTF-8" -e FONTCONFIG_PATH="/etc/fonts" -e ICU_DATA="/share/icu/59.1" -e LD_LIBRARY_PATH="/lib:/lib/samba:/system" -e LIBVA_DRIVERS_PATH="/lib/dri" -e UID="1001" -e GID="100" -e GIDLIST="2" -v "/home/dockerperson/.config/Emby":"/config":rw -v "/srv/dev-disk-by-label-HDD1/Share1/Film":"/Film":rw -v "/srv/dev-disk-by-label-HDD1/Share1/Serier":"/Serier":rw -v "/srv/dev-disk-by-label-HDD1/Share1/Downloads":"/Downloads":rw --name="Emby" "emby/embyserver_arm32v7:latest" 2>&1' with exit code '126': eaae314ad052b58953232ed37460b8d81fc61a4e0c72aa0ec173e46ef89e15c7 docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/init\": permission denied": unknown. in /usr/share/php/openmediavault/system/process.inc:175 Stack trace: #0 /usr/share/openmediavault/engined/rpc/docker.inc(587): OMV\System\Process->execute() #1 [internal function]: OMVRpcServiceDocker->runContainer(Array, Array) #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('runContainer', Array, Array) #4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'runContainer', Array, Array, 1) #5 {main}
-
Is this a potential bug?
I have a storage container named simply storage. I realized I made a mistake with one of the paths, so I copied it, corrected the error, and called it storage2. This container is visible in the Docker plugin, but it's not appearing in the drop-down list of containers when I attempt to mount it to another container. I've tried restarting the Docker service and rebooting the server:
-
The drop down menu catches only containers “created” if they are in running state, exited or stopped won’t pick. Check that first, maybe the copy command made it run.
-
Can you make multiple containers of the same program(ie qbitorrent) and just differentiate them via port and name?
-
Can you make multiple containers of the same program(ie qbitorrent) and just differentiate them via port and name?
Yes
-
The drop down menu catches only containers “created” if they are in running state, exited or stopped won’t pick. Check that first, maybe the copy command made it run.
I'll take a look when I get home. If I remember correctly, though, ALL storage containers are considered "stopped." You can see in the screenshot that the one storage container does appear.I had an issue with an earlier storage container that was somehow "converted" to a regular running container and would continuously restart. I got fed up with it and deleted it, which is when I created the one in use today.
I'll test and report back.
-
Yes
and I fail that this.
-
and I fail that this.
That sentence doesn’t help, your old enough in the forum to give that kind of answer.
-
That sentence doesn’t help, your old enough in the forum to give that kind of answer.
Sorry was interrupted at work,
I have attempted to set up a second Qbittorent docker container, We will call it Qbit-Movies. I set the Networking to Bridge, I give it the OMV IP with the following Host and custom ports 8081 and 6882 (default is 8080 and 6881) I set the PUID, GUID and the Drive locations.. Unfortunately when I attempt to connect to port 8081 it fails to load the page "This site can’t be reached 192.168.0.15 refused to connect."
-
Wrong mapping then. The container port should remain the same.
-
Wrong mapping then. The container port should remain the same.
Host or exposed?
-
Exposed port should be kept at default, and the host port can be changed.
Also, assuming you've used Linuxserver.io containers, make sure that both containers have unique /config folder mapping.
-
Exposed port should be kept at default, and the host port can be changed.
Also, assuming you've used Linuxserver.io containers, make sure that both containers have unique /config folder mapping.
Exposed port should be kept at default, and the host port can be changed.
Also, assuming you've used Linuxserver.io containers, make sure that both containers have unique /config folder mapping.
Thats what I was afraid of. I have 8080 and 6881 respectively for exposed and 8081 and 6882 for Host (see image below) and I get the following message (in Chrome) This page isn’t working
If the problem continues, contact the site owner. HTTP ERROR 401, I didn't even get a chance to put in the credentials yet. and blank pages in edge and IE. I thought maybe the port is being used so i tried port 26490 and got the same error -
Do not fill the host ip. And also there is log button should say something if container is not running properly inside.
-
Hi all - I'm new to docker and need a little help with the docker GUI plugin.
My question is how can I run an image using the plugin and get it to use the command '/bin/bash'
from the cli I can use:
docker run -i -t [imagename] /bin/bashHow do I do this using the GUI? When I try to start/run an image using the GUI it uses 'bash' as the command and the container does not start...
-
Hi all - I'm new to docker and need a little help with the docker GUI plugin.
My question is how can I run an image using the plugin and get it to use the command '/bin/bash'
from the cli I can use:
docker run -i -t [imagename] /bin/bashHow do I do this using the GUI? When I try to start/run an image using the GUI it uses 'bash' as the command and the container does not start...
I'm not an expert but i would think the extra arguments would be the spot for it.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!