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!

  • BiorixOPEnglish
    2•1 year ago

    Thank you

    So I read quickly and from what I understand I can generate a wiregard configuration file for example and provide it to this container, thus setting the network directly to the container.

    Am I understanding it correctly?

    • @breadsmasherEnglish
      3•1 year ago

      I can share my docker-compose later if you want. In short -

      you spin up your torrent container and vpn container

      you expose torrent ports on the vpn container

      you set the networking to route the torrent container to the vpn container

    • @njinxEnglish
      1•1 year ago

      That’s the gist of it. Although I’m not sure if it supports Wireguard. You’d want to check the readme first.