Rutorrent in docker

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Rutorrent in docker

      can someone point me in the right direction?
      I've a raid 5 in my nas and configured so sharedfiles is accessable when I'm trying to configure the docker container starts but I cannot access the webGUI of rutorrent. Is something wrong with this creation of the container?


      sudo docker create --name=rutorrent \
      --restart=always \
      -v /home/docker/rutorrent/config:/config \
      -v /sharedfolders/media/downloads:/downloads \
      -e PGID=1001 -e PUID=1001 \
      -e TZ=Europe/London \
      -p 82:82 -p 82:82 \
      -p 61318:61318 -p 61318:61318/udp \
      linuxserver/rutorrent

      Thanks in advance,
      B
    • duplicated ports, you only need one statement:

      -p 82:82 -p 82:82 \
      -p 61318:61318 -p 61318:61318/udp \

      must be:

      -p 82:82 -p 61318:61318 \
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ;
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife
    • somehow I cannot add the error message,
      here it is...

      Source Code

      1. root@openmediavault:~# sudo docker start rutorrent
      2. Error response from daemon: driver failed programming external connectivity on endpoint rutorrent (c20519eb543cc904e5bcef2a490df0ecf36229cd83153ae748b8614fb82e8442): Bind for 0.0.0.0:82 failed: port is already allocated
      3. Error: failed to start containers: rutorrent
      4. root@openmediavault:~#
    • Here is the docker container log

      @raulfg3 now i only stated the ports once.

      Brainfuck Source Code

      1. root@openmediavault:~# sudo docker create --name=rutorrent \
      2. > --restart=always \
      3. > -v /home/docker/rutorrent/config:/config \
      4. > -v /sharedfolders/media/downloads:/downloads \
      5. > -e PGID=1001 -e PUID=1001 \
      6. > -e TZ=Europe/London \
      7. > -p 84:84 -p 61318:61318 \
      8. > linuxserver/rutorrent
      9. eec60c9d3e3db37172d3cfa635e1ae276796dcdff9c91aab07dd1b7e5fed4987
      10. root@openmediavault:~# sudo docker start rutorrent
      11. rutorrent
      12. root@openmediavault:~# docker logs --details rutorrent
      13. [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
      14. [s6-init] ensuring user provided files have correct perms...exited 0.
      15. [fix-attrs.d] applying ownership & permissions fixes...
      16. [fix-attrs.d] done.
      17. [cont-init.d] executing container initialization scripts...
      18. [cont-init.d] 10-adduser: executing...
      19. -------------------------------------
      20. _ ()
      21. | | ___ _ __
      22. | | / __| | | / \
      23. | | \__ \ | | | () |
      24. |_| |___/ |_| \__/
      25. Brought to you by linuxserver.io
      26. We gratefully accept donations at:
      27. https://www.linuxserver.io/donations/
      28. -------------------------------------
      29. GID/UID
      30. -------------------------------------
      31. User uid: 1001
      32. User gid: 1001
      33. -------------------------------------
      34. [cont-init.d] 10-adduser: exited 0.
      35. [cont-init.d] 20-config: executing...
      36. [cont-init.d] 20-config: exited 0.
      37. [cont-init.d] done.
      38. [services.d] starting services
      39. [services.d] done.
      40. root@openmediavault:~#
      Display All

      The post was edited 1 time, last by bowe ().

    • Ok, but still do not work, because rutorrent use port 80 for webGUI, so config must be -p 84:80 -p 61318:61318 \


      please correct this and try co connect to http://<YourNasIP>:84


      PD: Please post what exact rutorrent docker do you use, because hub.docker.com/r/linuxserver/rutorrent/ use ports 80, 5000, 51413,6881 and not port 84 and 61318


      so you must understand how docker translate internal port to your external port:


      Display Spoiler

      Parameters
      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 8080http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ;
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife
    • @raulfg3

      I got it to work with your help, thank you!

      Can anyone point me in the right direction to get autodl-irssi installed? Docker is very confusing to me...

      Edit: Hmm, also can't seem to change the download location from my OS disc to my ZFS pool...
      Case: U-NAS NSC-810
      Motherboard: ASRock - C236 WSI Mini ITX
      CPU: Core i7-6700
      Memory: 32GB Crucial DDR4-2133

      The post was edited 1 time, last by elastic ().

    • elastic wrote:

      @raulfg3

      I got it to work with your help, thank you!

      Can anyone point me in the right direction to get autodl-irssi installed? Docker is very confusing to me...

      Edit: Hmm, also can't seem to change the download location from my OS disc to my ZFS pool...

      Can you try following my guide here to see if it all functions correctly? I don't talk about autodl there but at least you can make sure you can change the download location and general operation is successful.

      What happens when you try to change your download location on that container? I don't use ZFS, but I do use a mergerFS pool that requires certain options to be disabled before data can be written by rutorrent to the pool.
    • flvinny521 wrote:

      elastic wrote:

      @raulfg3

      I got it to work with your help, thank you!

      Can anyone point me in the right direction to get autodl-irssi installed? Docker is very confusing to me...

      Edit: Hmm, also can't seem to change the download location from my OS disc to my ZFS pool...
      Can you try following my guide here to see if it all functions correctly? I don't talk about autodl there but at least you can make sure you can change the download location and general operation is successful.

      What happens when you try to change your download location on that container? I don't use ZFS, but I do use a mergerFS pool that requires certain options to be disabled before data can be written by rutorrent to the pool.

      Thanks for taking the time to make such a thorough guide. Unfortunately I followed it and it does not work for me. It's still pointed at my OS disc and every time I restart the image, my settings change back to default in rutorrent itself.
      Case: U-NAS NSC-810
      Motherboard: ASRock - C236 WSI Mini ITX
      CPU: Core i7-6700
      Memory: 32GB Crucial DDR4-2133
    • elastic wrote:

      Thanks for taking the time to make such a thorough guide. Unfortunately I followed it and it does not work for me. It's still pointed at my OS disc and every time I restart the image, my settings change back to default in rutorrent itself.

      Have you marked the config folder as read-only?

      Can you show us screenshots of your container setup? Also, are you changing your download location in the rutorrent web UI, or in the rtorrent.rc file?
    • flvinny521 wrote:

      elastic wrote:

      @raulfg3

      I got it to work with your help, thank you!

      Can anyone point me in the right direction to get autodl-irssi installed? Docker is very confusing to me...

      Edit: Hmm, also can't seem to change the download location from my OS disc to my ZFS pool...
      Can you try following my guide here to see if it all functions correctly? I don't talk about autodl there but at least you can make sure you can change the download location and general operation is successful.

      What happens when you try to change your download location on that container? I don't use ZFS, but I do use a mergerFS pool that requires certain options to be disabled before data can be written by rutorrent to the pool.
      I don't believe I did to be honest. If that was one of the steps I may have over looked it. I also just realized that this thread is marked under OMV 4, I'm running 3. Would that make a difference? I'll post screen shots a bit later on as I already uninstalled it lol.
      Case: U-NAS NSC-810
      Motherboard: ASRock - C236 WSI Mini ITX
      CPU: Core i7-6700
      Memory: 32GB Crucial DDR4-2133
    • flvinny521 wrote:

      Nah, OMV 3 or 4 shouldn't make a difference here. If you want changes to be persistent between container restarts, you should change the settings in the rtorrent.rc file located in your config folder rather than changing the settings from within rutorrent itself. That may have been the problem.
      I've recently upgraded to OMV 4. I'd really love to get this working here as deluge really doesn't fit my needs anymore. I can get it installed and up and running as I was able to over the summer with OMV 3. However the same issue exists as I can not get this to use my ZFS pool. My ZFS pool is mounted as /Home

      [IMG:https://i.imgur.com/rf0HW0k.png]

      [IMG:https://i.imgur.com/IngRrez.png]

      [IMG:https://i.imgur.com/CP2SlX2.png]

      [IMG:https://i.imgur.com/6K7bxhj.png]

      [IMG:https://i.imgur.com/hKTZVCN.png]

      It seems that for some reason it's still using my OS drive for torrent storage. Also I can't even browse folders when adding a new torrent, which I'm guessing is some sort of permission issue.
      Case: U-NAS NSC-810
      Motherboard: ASRock - C236 WSI Mini ITX
      CPU: Core i7-6700
      Memory: 32GB Crucial DDR4-2133
    • gderf wrote:

      Within the application you have for Default directory for downloads set to /Home. This is incorrect. It must be /downloads.
      Always? Here's why I ask. My structure is
      /Home/Movies/Bunch of Movies in folders
      /TV/Bunch of Television Shows in folders
      /Music/Bunch of Albums in folders

      I need this structure for plex. How can I work around this then if it must always be /downloads for ruTorrent?

      Also before I proceed any further, is it possible to get autodl-irssi running with docker?
      Case: U-NAS NSC-810
      Motherboard: ASRock - C236 WSI Mini ITX
      CPU: Core i7-6700
      Memory: 32GB Crucial DDR4-2133
    • Within the application you can only use references to the Container paths. These are the only paths the container is aware of. But you may be able to create arbitrary ones and as many as you need. Try this and see if it works in the Volume and Bind mounts section of the container.

      Source Code

      1. Host path Container path
      2. /Home/Movies/ /Movies
      3. /Home/TV /TV
      4. /Home/Music /Music
      I don't use autodl-irssi so I have no answer for you.
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • gderf wrote:

      Within the application you can only use references to the Container paths. These are the only paths the container is aware of. But you may be able to create arbitrary ones and as many as you need. Try this and see if it works in the Volume and Bind mounts section of the container.

      Source Code

      1. Host path Container path
      2. /Home/Movies/ /Movies
      3. /Home/TV /TV
      4. /Home/Music /Music
      I don't use autodl-irssi so I have no answer for you.
      ......

      I think the problem was with the image that I was pulling. I followed the guide here and typed rutorrent, then installed the first result that popped up. It has been problematic for me for quite some time. I admit I'm sort of ignorant with linux and docker, so I chalked it up to a mistake on my part somewhere along the installation process.

      I got rid of it and tried another image. I browsed the repo and installed the image that I found there (that also included autodl-irssi) and everything works flawlessly the first try!

      The only thing I need to figure out how to do now is get a password on this client, figure out why the client does not remember ratios when I reboot and why I have a little red exclamation point telling me port 49161 is closed, despite me setting it in docker. Once I figure these out though I'm golden :)

      Thanks for your help and to everyone else that has helped me here. I think this whole ordeal has caused me to gray considerably lol....
      Case: U-NAS NSC-810
      Motherboard: ASRock - C236 WSI Mini ITX
      CPU: Core i7-6700
      Memory: 32GB Crucial DDR4-2133

      The post was edited 1 time, last by elastic ().