ventz / docker-openvpn Goto Github PK

The container isn't actually expecting anything in /data, in fact it specifically is not looking at /data but /etc/openvpn. /data is expected on the docker host, and only if you use the -v option exactly as it is at the bottom of the README. The existing wording could be confusing to people trying to map their OpenVPN configuration to /data inside the container instead of /etc/openvpn where it should be.

I appreciate your contribution, and would like to use it in my work. However, I do not find any license here, could you please clarify a bit on this topic?

I'm running this under Podman on a Fedora31 VM (Container wrapped by generated service file). I get odd behaviour that the container's net.ipv4.ip_forward flag resets to 0 after the hosting VM reboots.

I tried messing with the /etc/sysctl stuff (no apparent effect) and also rebuilding the container with the line in the Dockerfile with this setting uncommented (Whines about a read-only filesystem). I'm neither a docker, nor Alpine expert, though (obviously).

The only way I found around the issue was to either modify /start-vpn.sh to explicitly set the flag prior to OpenVPN. Or alternatively I can add an ExecStartPost clause in the hosting VM's service to force-in the flag from the outside.

You might want to change EXPOSE 1194 in the docker file to EXPOSE 1194/udp.

That should be all that is needed.

is there any console output?
i configure my server but there are no logs for this container