THIS IMAGE IS DEPRECATED. PLEASE USE THE MULTI-ARCH IMAGES AT linuxserver/rutorrent
The LinuxServer.io team brings you another container release featuring easy user mapping and community support. Find us for support at:
- forum.linuxserver.io
- IRC on freenode at
#linuxserver.io
- Podcast covers everything to do with getting the most from your Linux Server plus a focus on all things Docker and containerisation!
Popular rtorrent client with a webui for ease of use. Rutorrent
docker create --name=ruttorent \
-v <path to data>:/config \
-v <path to downloads>:/downloads \
-e PGID=<gid> -e PUID=<uid> \
-e TZ=<timezone> \
-p 80:80 -p 5000:5000 \
-p 51413:51413 -p 6881:6881/udp \
lsioarmhf/rutorrent-aarch64
The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side. For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container. So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.
-p 80
- the port(s)-p 5000
- the port(s)-p 51413
- the port(s)-p 6881/udp
- the port(s)-v /config
- where rutorrent should store it's config files-v /downloads
- path to your downloads folder-e PGID
for GroupID - see below for explanation-e PUID
for UserID - see below for explanation-e TZ
for timezone information, eg Europe/London
It is based on alpine linux with s6 overlay, for shell access whilst the container is running do docker exec -it rutorrent /bin/bash
.
Sometimes when using data 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 the data volume directory on the host is owned by the same user you specify and it will "just work" โข.
In this instance PUID=1001
and PGID=1001
. To find yours use id user
as below:
$ id <dockeruser>
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
IMPORTANT... THIS IS THE ARM64 VERSION
Webui can be found at <your-ip>:80
, configuration files for rtorrent are in /config/rtorrent and for the webui in /config/rutorrent/settings.
Settings, changed by the user through the "Settings" panel in ruTorrent, are valid until rtorrent restart. After which all settings will be set according to the rtorrent config file (/config/rtorrent/rtorrent.rc),this is a limitation of the actual apps themselves.
** Important note for user running services such as a webserver on port 80, change port 80 assignment **
** It should also be noted that this container when run will create subfolders ,completed, incoming and watched in the /downloads volume.**
Umask can be set in the /config/rtorrent/rtorrent.rc file by changing value in system.umask.set
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.
dht = disable
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..
use_udp_trackers = yes
peer_exchange = yes
-
Shell access whilst the container is running:
docker exec -it rutorrent /bin/bash
-
To monitor the logs of the container in realtime:
docker logs -f rutorrent
-
container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' rutorrent
- image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' lsioarmhf/rutorrent-aarch64
- 27.08.18: Add bind tools package.
- 22.08.18: Rebase to alpine 3.8.
- 10.01.18: Rebase to alpine 3.7.
- 28.10.17: Mediainfo moved from testing to community repo.
- 09.10.17: Use repo version of mediainfo to shorten build time.
- 30.05.17: Rebase to alpine 3.6.
- 03.05.17: Fix log permissions.
- 18.03.17: Note in readme about disabling dht in some circumstances.
- 24.02.17: Patch a source file to quash rss https bug.
- 12.12.16: Intial Release.