cross-posted from: https://lemmy.ml/post/4912475
https://codeberg.org/Strict3443/qbittorrent-i2p-vnc
I have created a Dockerfile which will compile the latest version of qBittorrent which has experimental I2P support into a docker container with VNC support. The reason for this is my server is headless and I wanted to use the v4.6.x version of qBittorrent, but the qbittorrent-nox version of v4.6.x does not have I2P options yet. So I had to build the GUI version on top of a VNC image.
In doing so, this will build a container that has VNC capabilities where you can utilize a desktop environment to setup the GUI version of qBittorrent with your I2P settings, and then just use the web-ui from there on.
Why?
I am a qBittorrent user and wanted to start downloading and cross-seeding torrents with I2P, so I built this image as a drop in replacement of my
linuxserver/qbittorrentdocker container and it just works.Why don’t you post the docker image?
I am not sure how yet, and I also left it as a Dockerfile so that you can build this on ARM or x86-64 depending on your needs
Note
This image can be quite heavy and take a long time to build, but until v4.6.x is out of beta, this will do.
Never head of I2P, sounds pretty cool. I’ve just stuck to encryption for torrents and haven’t had any complaints from my ISP.
Glad to see that working still! Torrenting over I2P is sort of a fail-safe option for people in somewhat oppressive places where VPNs may be illegal. Also, with the recent port-forwarding removal in Mullvad, this makes it harder moving forward to try and seed content without being able to make a direct connection with open ports.