I had things working per my comment on reddit: I don't think that having traefik take first global then local network (or the inverse) is a good solution, because there will always be cases that won't work if we do that. We should either introduce another label for this situation or find a way for traefik to decide which one to use. This was already highlighted by in the past. Which is unknown at the time of writing the `docker-compose.yml` file :) Traefik won't work because `` refers to a network declared in the file and not outside, hence its full name will be prefixed by the `docker-compose` project's name. var/run/docker.sock:/var/run/docker.sock "=Host:"Ĭommand: -docker.domain= always This means that with the following `docker-compose.yml` file: The expected result is the same IP as from inside the openvpn-client container.Īnd that’s it, really, a few steps but no rocket science.Basically, when using `` in a simple `docker-compose` situ … ation, it seems that the value passed to the label must include the full network name. The other is the “depends-on,” another failsafe mechanism.īefore starting downloading another Linux distro via torrent, let’s try the same connection test again from inside the qBt container: One is the network_mode, telling qBt to talk to the openvpn-client container. I created a persistent folder for the config files and mapped my downloads folder to the container.Īlso, there are two references to the VPN container. We’re forwarding 8080 from the VPN container. There are a few things which require special attention.įirst, I removed all port-related lines from the original compose files, as we don’t need them here. Image: lscr.io/linuxserver/qbittorrent:latest Is there even an alternative? I don’t think so. That’s it, and the VPN container part is alive. Portainer makes the verification pretty convenient.Īnd paste the following command into the console: wget -O -q echo Start the container either per CLI or Portainer. The result is a random high port, and you add it into the compose file as “forwarded ports.” Now we go back to Mullvad and select “Manage devices and ports,” scroll all down, and choose the same city and “no device.” Unzip it and throw the files via SSH into the /vpn folder. Select Linux and a country and city of your choice, and download the zip file. Once logged in, go to their OpenVPN configurator. Over at Mullvad, click My account and enter your unique account number. Let’s have a look inside: Get the config files from Mullvad I created a folder on the Docker host at /opt/mullvad/data/vpn and attached it to the container. The killswitch stays on as a security measure, and the subnet is my local subnet so that I can access it.Īt the bottom, we’re opening port 8080, which will be passed through to qBittorrent’s web interface later. We need the cap_add as the container requires permissions to create connections. Let me show you how to do it it’s easier than I thought: Mullvad VPN and qBittorrent in Docker. I’ve chosen Mullvad as my new VPN provider let’s see how it works out long-term! I couldn’t find anything turnkey, so I had to create my own. I no longer wanted to deal with this company and started looking for alternatives with a similar setup. I used their service for over a year for pure convenience a Docker stack for both their VPN service and qBittorrent exists and runs with a single compose deployment. The other day, I had the worst customer support experience with a company called NordVPN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |