It is possible to implement a killswitch inside the vpn container by using the up/down scripts for openvpn. By using these you can modify the firewall rules with iptables to enable/disable network connectivity for the container. I've done this quite long ago and don't remember the details 
If you want to have a look at my implementation it's merged in the linuxserver.io container here: https://github.com/linuxserver/docker-vpn I will not be able to support very much though...
Beiträge von nicjo814
-
-
can anybody help for a container update with cronjob?
See here regarding running Docker commands in cron: https://stackoverflow.com/ques…tart-inside-a-cron-script
-
The server is back up. Fix required though to prevent these issues in the future.
-
There is a great guide for using Docker here: OpenMediaVault Docker-GUI Plugin Usage [ x86_64 Arch only]
In your case it looks like you are using bridged mode networking. This works by giving each container it's private IP (172.17.0.X) which is not reachable from outside of docker. However you can use port forwarding to access the contanier (check the guide for how to configure this). When done you would be able to access the container via the IP of your host machine like 192.168.1.XXX:8080 or whichever port you forward.
-
I have to test this too. Haven't noticed it myself before.
-
Did you execute "docker logs -f" as root? Forgot to mention that it is required...
-
I'm afraid I don't have any arm boxes to play with so I can't test these images you are having issues with.
However I might have some ideas on how to fix your issues...
First try to run one of the "problem images" without mapping any volumes inside it. This should take care of any issues regarding permissions. If it starts and you can access it then you most likely had som permission issues.
Next I would try to make sure that all other containers are stopped before testing (i you are low on resources).
If it still doesn't work it might be a good idea to run "docker logs -f <name_of_the_container>" after having started a container to see if you can spot any errors.
Finally make sure that the IP you are assigning the container is actually within the macvlan network you have defined.
-
Perfect! Thanks for testing and reporting!
-
Working fine now! Thanks! =)
Without the patch?
-
I've reported the broken URL and it should be fixed now, so the patch should no longer be needed for this particular logo
-
OK, thanks for that.
I have created a patch that should fix the issue. Could you test with the version available here (it's for OMV 4.x):
https://www.dropbox.com/s/7nxd…er-gui_4.0.2_all.deb?dl=1 -
Just curious. What did you do there to trigger the problem?
I located the missing logo being for the linuxserver Lychee image. On my newly installed system I was missing the liuxserver_lychee.png and .sha files in the /var/www/openmediavault/images/dockerrepo/ directory. I copied the .sha file from another image in that directory and the problem appeared.
-
Nevermind, I've been able to recreate the issue here now.
-
I tried accessing the Docker service in Chromium browser incognito mode. It still throws that same error popup. And I have cleared the browser cache several times before too.
Firefox and Chrome browsers also throw that same error and I do not recall visiting that page ever in those.
From your signature I assume that you are running version 4.0.1 of the plugin?
-
Yep issue still there when i checked now..
Edit: i am trying to paste the exception here but en exception is thrown =)
Error #0:exception 'ImagickException' with message 'Imagick::__construct(): HTTP request failed! HTTP/1.1 404 Not Found' in /usr/share/openmediavault/engined/rpc/docker.inc:1504Stack trace:#0 /usr/share/openmediavault/engined/rpc/docker.inc(1504): Imagick->__construct('https://raw.git...')#1 [internal function]: OMVRpcServiceDocker->syncDockerLogos(NULL, Array)#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('syncDockerLogos', NULL, Array)#4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'syncDockerLogos', NULL, Array, 1)#5 {main}
I just did a clean installation of OMV4 and installed the docker plugin. I get no errors... It feels like there was some issue with one of the URL's to the logos and that you might have that information cached on your end somehow...
Could you try to access the plugin while in incognito mode in your browser?
-
Same here, still after having any updates done.
Ok, guess I have to look at this some more then
-
I've looked at this and don't get any error. Do you still have problems with the logos?
-
I have the exact same issue, discovered it after i restarted the server today. I dont really keep track of the updates i apply but i know Docker was updated the other week and i 'think' i received a kernel update as well.
OMV 3.0.95, kernel Linux 4.9.0-0.bpo.4-amd64 and Docker 17.12.0-ce.Do you still have this issue? I believe it should have been fixed now (the URL to the looks to be corrected).
-
It looks like one of the logos for the linuxserver.io images is pointing to an incorrect URL.
A fix would be to add error handling around that part of the code that downloads the logos. Quite simple fix, but I'm not able to do it in a couple of days.
-
It "should" be unrelated since the error says it's a 404 connecting to github...
I can't verify right now since I'm away from my nas the next couple of days without any proper Internet connection
