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!

  • Biorix@lemmy.fmhy.mlOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Hey ! Sorry I didn’t saw your message. I came here to explain how I solved it (just now)!

    I discovered a lot of nice option in gluetun (like port forwarding)

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

    Thanks for your help!

    • 子犬です@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      This is actually very helpful, maybe now I can seed to my private trackers! Lol

      I’ve been having to use a seed box for those torrents.

      So just to be clear, you set up Gluetun, port forwarding on Gluetun, set the port # on qBittorrent, AS WELL AS changing the adapter on qBittorrent?