kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Templated Files
rodzic
8ed6b54853
commit
0eab5da6ac
|
@ -1,6 +1,12 @@
|
||||||
# linuxserver/rutorrent
|
# [linuxserver/rutorrent](https://github.com/linuxserver/docker-rutorrent)
|
||||||
|
|
||||||
[](https://discord.gg/YWrKVTn) [](https://microbadger.com/images/linuxserver/rutorrent) [](https://microbadger.com/images/linuxserver/rutorrent)   [](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-rutorrent/job/master/) [](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/rutorrent/latest/index.html)
|
[](https://discord.gg/YWrKVTn)
|
||||||
|
[](https://microbadger.com/images/linuxserver/rutorrent "Get your own version badge on microbadger.com")
|
||||||
|
[](https://microbadger.com/images/linuxserver/rutorrent "Get your own version badge on microbadger.com")
|
||||||
|

|
||||||
|

|
||||||
|
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-rutorrent/job/master/)
|
||||||
|
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/rutorrent/latest/index.html)
|
||||||
|
|
||||||
[Rutorrent](https://github.com/Novik/ruTorrent) is a popular rtorrent client with a webui for ease of use.
|
[Rutorrent](https://github.com/Novik/ruTorrent) is a popular rtorrent client with a webui for ease of use.
|
||||||
|
|
||||||
|
@ -13,18 +19,19 @@ Simply pulling `linuxserver/rutorrent` should retrieve the correct image for you
|
||||||
The architectures supported by this image are:
|
The architectures supported by this image are:
|
||||||
|
|
||||||
| Architecture | Tag |
|
| Architecture | Tag |
|
||||||
| :---: | :--- |
|
| :----: | --- |
|
||||||
| x86-64 | amd64-latest |
|
| x86-64 | amd64-latest |
|
||||||
| arm64 | arm64v8-latest |
|
| arm64 | arm64v8-latest |
|
||||||
| armhf | arm32v7-latest |
|
| armhf | arm32v7-latest |
|
||||||
|
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
|
||||||
Here are some example snippets to help you get started creating a container from this image.
|
Here are some example snippets to help you get started creating a container from this image.
|
||||||
|
|
||||||
### docker
|
### docker
|
||||||
|
|
||||||
```text
|
```
|
||||||
docker create \
|
docker create \
|
||||||
--name=rutorrent \
|
--name=rutorrent \
|
||||||
-e PUID=1000 \
|
-e PUID=1000 \
|
||||||
|
@ -39,6 +46,7 @@ docker create \
|
||||||
linuxserver/rutorrent
|
linuxserver/rutorrent
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
### docker-compose
|
### docker-compose
|
||||||
|
|
||||||
Compatible with docker-compose v2 schemas.
|
Compatible with docker-compose v2 schemas.
|
||||||
|
@ -66,40 +74,43 @@ services:
|
||||||
|
|
||||||
## Parameters
|
## Parameters
|
||||||
|
|
||||||
Docker images are configured using parameters passed at runtime \(such as those above\). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
|
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
|
||||||
|
|
||||||
### Ports \(`-p`\)
|
### Ports (`-p`)
|
||||||
|
|
||||||
| Parameter | Function |
|
| Parameter | Function |
|
||||||
| :---: | :--- |
|
| :----: | --- |
|
||||||
| `80` | ruTorrent Web UI |
|
| `80` | ruTorrent Web UI |
|
||||||
| `5000` | scgi port |
|
| `5000` | scgi port |
|
||||||
| `51413` | Bit-torrent port |
|
| `51413` | Bit-torrent port |
|
||||||
| `6881/udp` | Bit-torrent port |
|
| `6881/udp` | Bit-torrent port |
|
||||||
|
|
||||||
### Environment Variables \(`-e`\)
|
|
||||||
|
### Environment Variables (`-e`)
|
||||||
|
|
||||||
| Env | Function |
|
| Env | Function |
|
||||||
| :---: | :--- |
|
| :----: | --- |
|
||||||
| `PUID=1000` | for UserID - see below for explanation |
|
| `PUID=1000` | for UserID - see below for explanation |
|
||||||
| `PGID=1000` | for GroupID - see below for explanation |
|
| `PGID=1000` | for GroupID - see below for explanation |
|
||||||
|
|
||||||
### Volume Mappings \(`-v`\)
|
### Volume Mappings (`-v`)
|
||||||
|
|
||||||
| Volume | Function |
|
| Volume | Function |
|
||||||
| :---: | :--- |
|
| :----: | --- |
|
||||||
| `/config` | where ruTorrent should store it's config files |
|
| `/config` | where ruTorrent should store it's config files |
|
||||||
| `/downloads` | path to your downloads folder |
|
| `/downloads` | path to your downloads folder |
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## User / Group Identifiers
|
## User / Group Identifiers
|
||||||
|
|
||||||
When using volumes \(`-v` flags\), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
|
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
|
||||||
|
|
||||||
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
|
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
|
||||||
|
|
||||||
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
|
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
|
||||||
|
|
||||||
```text
|
```
|
||||||
$ id username
|
$ id username
|
||||||
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
||||||
```
|
```
|
||||||
|
@ -120,18 +131,22 @@ Umask can be set in the /config/rtorrent/rtorrent.rc file by changing value in `
|
||||||
|
|
||||||
If you are seeing this error `Caught internal_error: 'DhtRouter::get_tracker did not actually insert tracker.'.` , a possible fix is to disable dht in `/config/rtorrent/rtorrent.rc` by changing the following values.
|
If you are seeing this error `Caught internal_error: 'DhtRouter::get_tracker did not actually insert tracker.'.` , a possible fix is to disable dht in `/config/rtorrent/rtorrent.rc` by changing the following values.
|
||||||
|
|
||||||
```text
|
```shell
|
||||||
dht = disable
|
dht = disable
|
||||||
peer_exchange = no
|
peer_exchange = no
|
||||||
```
|
```
|
||||||
|
|
||||||
If after updating you see an error about connecting to rtorrent in the webui, remove or comment out these lines in /config/rtorrent/rtorrent.rc ,whatever value is set, yes or no. Just setting them to no will still cause the error..
|
If after updating you see an error about connecting to rtorrent in the webui,
|
||||||
|
remove or comment out these lines in /config/rtorrent/rtorrent.rc ,whatever value is set, yes or no.
|
||||||
|
Just setting them to no will still cause the error..
|
||||||
|
|
||||||
```text
|
```
|
||||||
use_udp_trackers = yes
|
use_udp_trackers = yes
|
||||||
peer_exchange = yes
|
peer_exchange = yes
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Support Info
|
## Support Info
|
||||||
|
|
||||||
* Shell access whilst the container is running:
|
* Shell access whilst the container is running:
|
||||||
|
@ -169,4 +184,3 @@ peer_exchange = yes
|
||||||
* **07.08.16:** - Perms fix on nginx tmp folder, also exposed php.ini for editing by use in /config/php.
|
* **07.08.16:** - Perms fix on nginx tmp folder, also exposed php.ini for editing by use in /config/php.
|
||||||
* **26.07.16:** - Rebase to alpine.
|
* **26.07.16:** - Rebase to alpine.
|
||||||
* **08.03.16:** - Initial Release.
|
* **08.03.16:** - Initial Release.
|
||||||
|
|
||||||
|
|
Ładowanie…
Reference in New Issue