This causes trouble because OpenVPN will not be able to resolve the host to connect to. Some have encountered problems with DNS resolving inside the docker container. Known issues, tips and tricks Use Google DNS servers You can run it using the command below or have a look in the repository proxy folder for inspiration for your own custom proxy. There is a reverse proxy being built with the container. For instance if your local network uses the IP range 192.168.0.0/24 you would pass -e LOCAL_NETWORK=192.168.0.0/24.Īlternatively you can reverse proxy the traffic through another container, as that container would be in the docker range. The container supports the LOCAL_NETWORK environment variable. 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 To use this env file, use the following to run the docker image:īut what's going on? My isn't responding? 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. Multiple networks can be added, comma separated. Sets the local network that should have access. Supported providers and their config values are listed in the table above.
#Configure sabnzbd with newshosting vpn 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. If no config is given, a default config will be selected for the provider you have chosen.įind available OpenVPN configurations by looking in the openvpn folder of the GitHub repository.Īs you can see, the container also expects a data volume to be mounted. The OPENVPN_CONFIG is an optional variable. You must set the environment variables OPENVPN_PROVIDER, OPENVPN_USERNAME and OPENVPN_PASSWORD to provide basic connection details. $ docker run -privileged -d -name CONTAINER_NAME \