To your request will be treated as "non-local" traffic and therefore be routed out through the VPN interface. This is because the VPN is active, and since docker is running in a different ip range than your client the response $ docker run -cap-add=NET_ADMIN -device=/dev/net/tun -d \īut what's going on? My isn't responding? To use this env file, use the following to run the docker image: variables on the command line these will override the ones in the env file. You can use this to create local configurationsīy filling in the details and removing the # of the ones you want to use. In the GitHub repository there is a provided DockerEnv file with all the current transmission and openvpn environment variables. Sets the group id for the transmission userĪnother way is to use a docker env file where you can easily store all your env variables and maintain multiple configurations for different providers. Sets the user id who will run transmission You may set the following parameters to customize the user id that runs transmission. However, it is possible to change who runs the transmission process. User configuration optionsīy default everything will run as the root user.
PS: TRANSMISSION_BIND_ADDRESS_IPV4 will be overridden to the IP assigned to your OpenVPN tunnel interface. The environment variables are the same name as used in the transmission settings.json fileĪnd follow the format given in these examples: Transmission variable nameĪs you can see the variables are prefixed with TRANSMISSION_, the variable is capitalized, and - is converted to _. You may override transmission options by setting the appropriate environment variable. If TRANSMISSION_PEER_PORT_RANDOM_ON_START is enabled then it allows traffic to the range of peer ports defined by TRANSMISSION_PEER_PORT_RANDOM_HIGH and TRANSMISSION_PEER_PORT_RANDOM_LOW. When enabled, the firewall blocks everything except traffic to the peer port and traffic to the rpc port from the LOCAL_NETWORK and the internal docker gateway. Sets the local network that should have access. Supported providers and their config values are listed in the table above.
#Airvpn custom directives torrent#
torrent files.īy default a folder named transmission-home will also be created under /data, this is where Transmission stores its state. This is where Transmission will store your downloads, incomplete downloads and look for a watch directory for new. e "OPENVPN_CONFIG=ipvanish-AT-Vienna-vie-c02"Īs you can see, the container also expects a data volume to be mounted. The container is available from the Docker registry and this is the simplest way to get it.
#Airvpn custom directives update#
When using PIA as provider it will update Transmission hourly with assigned open port. It bundles certificates and configurations for the following VPN providers: Provider Name Docker container which runs Transmission torrent client with WebUI while connecting to OpenVPN.
0 kommentar(er)
