docker-qbittorrent VS openvpn-client

Say I wanted to run this container on k3s. How do I specify PUID, PGID, WEBUI_PORT, and the volumes? This is literally the only thing keeping me from jumping headfirst into k3s. I have no intention of running anything docker in the near future and onwards, but I need to know how I can switch without using something like kompose (I don't want to trust a script with my deployment options, I want to do it by hand like I used to with Docker).

Here is a link to an issue I found on the linuxserver/docker-qbittorrent repo discussing the issue I'm currently having.

# https://github.com/linuxserver/docker-qbittorrent qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent network_mode: service:nordvpn environment: - PUID=13002 - PGID=13000 - TZ=${TIMEZONE} - UMASK=002 volumes: - ${ROOT_DIR}/docker/qbittorrent-config:/config - ${ROOT_DIR}/data/torrents:/data/torrents restart: unless-stopped depends_on: - vpn

In "docker ps" you'll see the EXPOSE Ports defined in the Dockerfile of your Image. They are only accessable in their own networks unless you just bridge your container to your host's network (not recommended).

My only issue is the the linuxserver/qbittorrent container doesn't always start up after a server reboot, I've just filed a github issue about this: https://github.com/linuxserver/docker-qbittorrent/issues/167

Check out the GitHub... Nine times out of ten the info is there: https://github.com/linuxserver/docker-qbittorrent

qBittorrent

Stuck on the Login page · Issue #109 · linuxserver/docker-qbittorrent (github.com)

I use dperson/openvpn-client, which seems to do the trick for the most part. Ive got several packages that route through it using network_mode: "service:openvpn".

Gluetun has an integrated killswitch: https://github.com/qdm12/gluetun

I used to use https://github.com/dperson/openvpn-client which has a killswitch as well.

By kill-switch I mean iptables rules that don't let anything out if there's no VPN interface up. So you don't run the risk of leaking torrent stuff through your plain-text connection.

One of my Pi servers running a series of Docker services was taken out a few months back because an apt upgrade changed the compilation target of time_t causing me to have to spend a week untangling a web of dependencies to revert to an older version of musl.

I just tested the https://github.com/dperson/openvpn-client to use my NordVPN account and could get it working, the container connects succesfully! Can I somehow share this connection to other LAN devices (eg my TV) where I cant't install a VPN client?

I have gone down a rabbit hole today trying to route all Docker container traffic through OpenVPN. Previously I have used dperson/openvpn-client, but I would prefer to run OpenVPN directly on the host. With the VPN up on the host, the Docker containers make use of the VPN connection but if it drops they continue without it. Ideally there would be a kill switch to prevent this from happening.

I am looking to use my protonvpn subscription to use with an OpenVPN container (this one), but the documentation on both Protonvpn and the repo is pretty light on how to use it.

Hey there, I successfully managed to run this OpenVPN docker Container on my DS218+. I then connected another container to use this OpenVPN container as a network. Everything works like a charm.

OpenVPN client to route my illicit content through Pakistan (CyberGhost paid VPN)

As someone who's currently using dperson/openvpn-client with a Cyberghost VPN, what are the advantages of this container?

I'd like to integrate an application on a container that's connected to an OpenVPN server. I've found a convenient client base image to build on top of, but I can't seem to find the right way to do this.