Of course not. Very few
Sent from my ASUS_Z017DA using Tapatalk
Of course not. Very few
Sent from my ASUS_Z017DA using Tapatalk
I used to be on a EXT4 filesystem for my storage drive, but docker just refused to load on that filesystem.
i have modified /etc/default/docker to make it work:
Now, i converted my storage to BTRFS and need to undo the changes i made in /etc/default/docker.
Anyone knows what is the default DOCKER_OPTS= is?
Thanks
By default all options are commented out, except for the omv plugin extra options of API tcp listening port
Of course not. Very few
If you want to have the full docker stack under a UI, you should consider then using portainer, which even has support for swarm cluster i believe.
Looks good @subzero79 - just installed - took a moment to realize I had to upload the plugin then go to the updates section to actually upgrade to it. I also had to force a reload on the browser to see the new options available.
1 question - what did you mean by "Now the modify button retains the extra options"? Was this in reference to the Extra Args section at the bottom? I wasn't aware these might be wiped out if I hit modify, so I wouldn't know any wiser. Just curious what this meant.
The extra arguments down bottom field wasn't able to retain any when modify or copy. That was an issue, maybe not an issue more like feature request. Only new containers created with the new version will retain btw.
Ok got it. Thanks for the clarification. I hadn't had any containers using the extra args so it didn't apply to me. Funny enough though, I just spun up a Unifi Video Controller container and it did require some extra args. So I was able to test that out and can confirm that is working as expected. Made some changes to the container and the extra args stayed intact.
Awesome work @subzero79 - thanks for the efforts!
Alles anzeigenIt is a problem with docker and my updated kernel (4.8) and aufs
The simplest workaround is to do
1) Install docker
apt-get install docker-engine
2) Try to see that docker doesn't start
/usr/bin/dockerd
3) Move one file from docker (for aufs) so docker won't complain about aufs
mv /var/lib/docker/aufs /var/lib/docker/aufs_bk
4) See that docker starts normally
/usr/bin/dockerd
Hey guy, you helped me a lot. I tried to get the docker plugin working for the last 4 days and then found your post on google... I've got the same problem on Kernel 4.9.
Use overlayfs , because aufs is not compatible with newer kernels.
I struggled a little until I understood that
Sent from my ASUS_Z017DA using Tapatalk
Is this potentially why I ran into an issue using MergerFS based filesystem mounts, for storing the docker container data? Aka the core configs being used to read/write just for starting up?
I noticed this was an issue and switched to mounting these locations via the physical device mount instead of the UFS mount. But when it comes to things like the media being used, it didn't have issues with UFS mounts.
Ive added now a clear log button. You can download here
There is no clear log switch in docker-engine, this goes against the normal usage of docker as is manual intervention of the docker folder.
I'll have to go grab that update and test it out. That can prove useful when troubleshooting and/or testing out new containers or container updates! Awesome work @subzero79!!
Good afternoon all.
I have a problem with docker-gui plugin. If I put this to /etc/default/docker, the docker gui doesn't show the images and containers:
DOCKER_OPTS="-H=0.0.0.0:2376 --tlsverify --tlscacert=/root/docker_tls/ca.pem --tlscert=/root/docker_tls/server-cert.pem --tlskey=/root/docker_tls/server-key.pem"
Could somebody help me to configure this for both working remote access and working gui as well?
Probably the plugin can't connect with tls.
I am using the latest OMV3 and docker-gui plugin.
Don't think the plugin supports tls, is hard coded to curl with plain http.
Thank you for the answer, it would be good to include this feature to the plugin. Docker don't allow the remote connection without TLS.
For curl this needs to be used with TLS(port 2376 is a convention):
curl https://$HOST:2376/images/json
\ --cert ~/.docker/cert.pem
\ --key ~/.docker/key.pem
\ --cacert ~/.docker/ca.pem
I've modified the curl inside the code to use tls. But I have no idea how to implement it as an option. This is a feature that not all users requires, the docker daemon runs in local host by default, tls would be necessary for exposing it to the wan side. Not sure if that's the case for everyone here. In omv4 with php7 the API call will be probably done to the unix socket.
I've added a small gui improvement, the macvlan dropdown menu now displays the corresponding subnet
BTW I am waiting for some feedback on this package....any bugs detected or similar, before submitting PR to the omv-extras repository.
@subzero79 - I've not run into any issues since running it. My systems are running great, and I recreated all of them using the GUI to the "unless stopped" restart policy.
One thing I would point out if it makes sense to dig into with your PR - is an issue I've uncovered recently. I'll link it HERE from the OMV forum post. Let me know if this should be created as an issue on the GH page instead and I'll be happy to open there. Just wasn't sure if it's something that may be in the same code set as what you were making changes to in your PR. Or if you just want to separate anyhow as it's a fix rather than an enhancement.
I've updated the package for the plex link error.
Hmm ... tried to grab it from the link in your previous post, but it says the file isn't there? New version # perhaps altered the link?
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!