Github/docker-qBittorrentvpn
1
0
Fork 0
mirror of https://github.com/MarkusMcNugen/docker-qBittorrentvpn synced 2024-11-22 18:45:25 +00:00
Code Issues Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Kristian Haugene 2014-11-09 17:43:26 +01:00
parent bdd2e3505c
commit 5e3a3ed56d
1 changed files with 18 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@ -14,7 +14,7 @@ docker build -t="docker-transmission-openvpn" .
``` ```
### Run it: ### Run it:
``` ```
sudo docker run --privileged -d -v /your/storage/path/:/data -p 9091:9091 docker-transmission-openvpn docker run --privileged -d -v /your/storage/path/:/data -p 9091:9091 docker-transmission-openvpn
``` ```
This will build the image with default settings. What this means is that the VPN connects to PIA Netherlands with your credentials, starts Transmission WebUI with authentication disabled and Transmission will store your torrents to /your/storage/path/completed. Transmission assumes "completed, incomplete and watch" exists in /your/storage/path This will build the image with default settings. What this means is that the VPN connects to PIA Netherlands with your credentials, starts Transmission WebUI with authentication disabled and Transmission will store your torrents to /your/storage/path/completed. Transmission assumes "completed, incomplete and watch" exists in /your/storage/path
@ -22,7 +22,7 @@ This will build the image with default settings. What this means is that the VPN
### But I want to provide my own Transmission settings! ### But I want to provide my own Transmission settings!
OK, so you're advanced. If you want to change the Transmission settings from the defaults, create your own settings.json file or base it on the default config. Then make the container use it like this: OK, so you're advanced. If you want to change the Transmission settings from the defaults, create your own settings.json file or base it on the default config. Then make the container use it like this:
``` ```
sudo docker run --privileged -d -v /your/storage/path/:/data -v /your/path/to/settings.json:/etc/transmission-daemon/settings.json -p 9091:9091 docker-transmission-openvpn docker run --privileged -d -v /your/storage/path/:/data -v /your/path/to/settings.json:/etc/transmission-daemon/settings.json -p 9091:9091 docker-transmission-openvpn
``` ```
The container will now use your local settings.json file for its configuration. The container will now use your local settings.json file for its configuration.
@ -55,4 +55,19 @@ http {
Your Transmission WebUI should now be avaliable at "your.host.ip.addr:8080/transmission/web/". Your Transmission WebUI should now be avaliable at "your.host.ip.addr:8080/transmission/web/".
Change the port in the docker run command if 8080 is not suitable for you. Change the port in the docker run command if 8080 is not suitable for you.
Good luck! ### What if I want to run the container interactively.
If you want do have access inside the container while running, do like this.
```
docker run --privileged -v /mnt/disk1/Torrents/:/data -p 9091:9091 -it --entrypoint=/bin/bash docker-transmission-openvpn
```
This will start the container and give you a bash shell to work from. The container has screen installed, so you can use screen to start supervisord which starts openVPN and Transmission. Then you can detach from screen and continue to use bash inside the running container. If you're unfamiliar with screen, read up on it. The commands are as follows:
```
screen
```
Accept the terms, then run supervisord and detach.
```
/usr/bin/supervisord
CTRL+A + d
```
You should now be detached and both services should be running.