dockerMullvadVPN VS docker-php-nginx

I used this guide to make a docker compose with qbittorrent bound through openvpn. I've had no issues with speed.

This is something that was worrying me a bit. I thought about running a sidecar but not sure. I found this and this and was hoping one of them would work, but I'll see this once I get to it.

Hi there, I'm setting up a docker config to use mullvad via openvpn following this tutorial

Or a more manual approach with more options: https://github.com/nickkjolsing/dockerMullvadVPN/blob/master/README.md

I set up a Mullvad docker container and a transmission docker container, routed through the Mullvad. I tested a 5 GB download, expecting router would see the traffic as TLS. It saw it as DNS. It sees nothing it considers torrent traffic.

After several hours of tinkering I managed to finally have a docker container running in container station that has access to the internet and is finally using my mullvad-openvpn configuration files. I've used this tutorial, which is not QNAP specific https://github.com/nickkjolsing/dockerMullvadVPN/blob/master/README.md I followed the steps and created a compose file, using the +Application function in Container Station GUI The Container starts up and connects to the vpn server flawlessly. I know that, because in the console I can see the OpenVPN message: "Initialization Sequence Completed" However, before I can /bin/sh into the container to confirm if the container is really connecting to the internet through VPN tunnel, the container keeps resetting itself. It just stops for a few seconds, and then starts up again, establishing connection to the vpn service provider (mullvad). I already tried different options in the compose file in line restart: unless-stopped (I tried: always and never) But it does not changes the behaviour. I know I do not have much memory (TS251+, 2GB RAM) But one openvpn container should be managable

Here's the instructions that I followed: https://github.com/nickkjolsing/dockerMullvadVPN

You can't compare that... your image is just another fpm/nginx combo ... plenty of these around

simple light weight

It's a question of ressource allocation / scalability desires vs ease of deployment... php ships an apache image ready to go docker pull php:apache. Personally I would prefer using a php-fpm/nginx hybrid for performance ... something like this

I have a dull day at work, so i'm going to play around with trying to get it running based on (this)[https://hub.docker.com/r/trafex/php-nginx] image.

I think I found a decent starting point: https://github.com/TrafeX/docker-php-nginx