I’m trying to link a docker container qFlood to my VPN (proton) on the host to prevent IP leaks.

When everything is on the host, I can just choose “proton0” in the network interface to use, but I don’t know how to do that inside the container because this interface is not exposed to the container.

Is there a way to do that?

Or even to implement the VPN inside a container?

What the alternative to prevent IP leaks with qBit on docker?

edit:

I used gluetun + qFlood as advised and it worked like a charmed except that I could’t seed or leach at all

Turns out the solution was to change the network interface in qBittorrent options from eth0 to tun0… Simple as that

Thank you all for the help!

  • @[email protected]English
    4•1 year ago

    I’m not sure about containers, but in Qbittorrent, Settings, Advanced, there is a “Network Interface” setting you can use to force qbit to only use a particular network interface. My VPN has it’s own network interface, so if it drops out, qbittorrent just stops downloading until the VPN comes back up. So, no IP leaks. Hopefully this helps you out a bit!

    • BiorixOPEnglish
      2•1 year ago

      Thank you

      I know the option but the network interface of the vpn is not accessible by the container.

      I’m trying to have this interface listed in the setting you mentioned