You can run qBittorrent outside docker and configure it to only bind to the network interface for the VPN (in Tools->Options->Advanced->Network Interface).
Unless for some strange reason your VPN connection is constantly renaming the network interface when it starts, this should work fine and make sure qBittorrent never sends any data outside the VPN connection.
This is Linux, so there’s usually more than one way to get the same result.
My torrent client is running in docker on my NAS, so running it outside of docker is a no-go. I switched back to my old setup of using a docker container that combines both qbittorrent and openvpn in the same container. Smooth sailing with no hitches at all. I can’t share the VPN across containers anymore, but qbittorrent was the only container that actually needed it.
Maybe I’ll get it working one day. Today is just not that day.
You can run qBittorrent outside docker and configure it to only bind to the network interface for the VPN (in Tools->Options->Advanced->Network Interface).
Unless for some strange reason your VPN connection is constantly renaming the network interface when it starts, this should work fine and make sure qBittorrent never sends any data outside the VPN connection.
This is Linux, so there’s usually more than one way to get the same result.
My torrent client is running in docker on my NAS, so running it outside of docker is a no-go. I switched back to my old setup of using a docker container that combines both qbittorrent and openvpn in the same container. Smooth sailing with no hitches at all. I can’t share the VPN across containers anymore, but qbittorrent was the only container that actually needed it.
Maybe I’ll get it working one day. Today is just not that day.