Open noideaman opened 1 year ago
A possible option would be to use swizzin if you want wireguard support. It configures your operating system instead of creating a docker container. You can use iptables to allow certain ports to bypass the PIA VPN. I have experience with this concept and have obtained a working configuration. If you have any questions, you can come on discord and ping Vertex.
XFS will have performance issues with rTorrent metadata processing. I recommend EXT4 for significantly higher performance. The torrent metadata is written to the disk in raw format. XFS does handle many small files very well compared to EXT4.
Support guidelines
I've found a bug and checked that ...
Description
Using docker-compose and adding the containers to the same network as a PIA vpn container to route torrent traffic. When PIA gives out an open port for port-forwarding/rtorrent incoming connections we as users of their service do not have control over the opened port. I got to the point the forwarded port works on other services and i can output the data into a plain text file.
How would we go about getting this configured in the rtorrent container? Can I mount the /etc/rtorrent/.rtorrent.rc file into another container and have the file updated by the external one?
Expected behaviour
A way to obtain the opened port and let rtorrent access it, even on changes
Actual behaviour
defaults to default port of 50000
Steps to reproduce
N/A
Docker info
Version
docker-compose --version
): (using docker compose not docker-compose) Docker version 20.10.22, build 3a2c30buname -a
):Linux box 6.1.4-1.el9.elrepo.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jan 4 18:19:21 EST 2023 x86_64 x86_64 x86_64 GNU/LinuxDocker compose
Container logs
N/A
Additional info
No response