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!

  • 子犬です@lemmy.worldEnglish
    1·
    1 year ago

    So I was wondering if you solved this?

    If not, maybe try the qBittorrent image from LinuxServer instead?

    I had your same problem that everything was stalled but switching to LinuxServer image fixed it :)

    Also, I just had this issue as well, make sure you use port forwarding on whatever VPN you have!

    I believe Gluetun has native support for Proton, so all you should need is to add “VPN_PORT_FORWARDING=on” to your environment on Gluetun container, and it will give you a port number. Put that port number in qBittorrent in the “Listening” port and you should be able to seed too! :)

    Lemme know if you have any other questions, and I’ll do my best to help :)

    • Biorix@lemmy.fmhy.mlOPEnglish
      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!