This repository has been archived by the owner on Jan 16, 2020. It is now read-only.
docker-compose yml example ? #13
Comments
|
You have a nice docker example here : https://github.com/xataz/docker-rtorrent-rutorrent#advanced-launch Do you really need a docker-compose.yml example, can you adapt-it yourself.. ? |
|
Hi Jérémy,
thanks for answering ! (Based on your name, I believe we might want to continue this discussion in French?)
First of all let me explain to you how all my different apps currently works.
each of my apps are hosted in a different container and a specific vhost has been created in nginx to enable them behind a reverse proxy.
I run nginx to listen to port 80 + redirect all traffic to port 443 to force all my apps to run exclusively in https, and listen to my apps who are only reachable on localhost:port.
if I take jackett as an example, the docker compose looks like this :
jackett:
image: linuxserver/jackett
container_name: jackett
restart: unless-stopped
network_mode: "bridge"
ports:
- '127.0.0.1:9117:9117'
environment:
- PUID=1001
- PGID=1001
volumes:
- './jackett:/config'
- '/home/plexuser/downloads:/downloads'
- '/etc/localtime:/etc/localtime:ro'
jackett is therefore only reachable through my localhost, and nginx is reverse proxying it like this :
server {
listen [::]:443 ssl;
listen 443 ssl;
server_name jackett.mydomain.com;
location / {
proxy_pass http://127.0.0.1:9117;
#Next three lines allow websockets
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; # managed by Certbot
}
This works very well for all my different apps. But I’m a little struggling as I have to configure ports for both rtorrent and rutorrent this time…
As for now, My docker-compose yml content looks like this for the rtorrent service :
rtorrent:
image: xataz/rtorrent-rutorrent
container_name: rtorrent
restart: always
network_mode: "bridge"
tty: true
ports:
- '127.0.0.1:45000:45000'
- '127.0.0.1:3001:3001'
environment:
- UID=1001
- GID=1001
volumes:
- '/home/plexuser/downloads:/data’
- '.rtorrent:/config’
So what I'm trying to reach here is the right yml in order to make it work in my current setup.
FYI, I’ve already created the nginx reverse proxy entry like this :
server {
listen [::]:443 ssl;
listen 443 ssl;
server_name rtorrent.mydomain.com;
location / {
proxy_pass http://127.0.0.1:3001;
#Next three lines allow websockets
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; # managed by Certbot
}
Port 3001 can of course be changed to anything else…I don’t care ;)
Could you help me adapt my rtorrent section in my yml file ? :/
thanks again !!!
… On 7 May 2018, at 11:36, Jérémy ***@***.***> wrote:
You have a nice docker example here : https://github.com/xataz/docker-rtorrent-rutorrent#advanced-launch <https://github.com/xataz/docker-rtorrent-rutorrent#advanced-launch>
Do you really need a docker-compose.yml example, can you adapt-it yourself.. ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0q7LE4Z9LjmUOgYTkv1qu1TYB77tMks5twBW7gaJpZM4T0kyf>.
|
|
You must use 8080 to reach your ruTorrent interface, well : And btw, yeh im french ;) |
|
Oh yes ! I did change my yml to :
rtorrent:
image: xataz/rtorrent-rutorrent
container_name: rtorrent
restart: always
network_mode: "bridge"
tty: true
ports:
- '127.0.0.1:45000:45000'
- '127.0.0.1:8080:8080'
environment:
- UID=1001
- GID=1001
- TZ=Europe/Paris
volumes:
- './rtorrent:/config'
- '/home/plexuser/downloads:/data’
and now I finally see rutorrent UI running ! thanks for that !
But now rutorrent still isn’t connected to the rtorrent running inside the container. I’m getting a bad response from server message. Bad response from server: (0 [error,list])
What am I supposed to do to fix this ? I see you did put a lot of ports in your run container example, therefore i’m a little bit confused (this is my first rtorrent/rutorrent install) :/
Thanks again !! I’m almost there ;)
… On 7 May 2018, at 12:05, Jérémy ***@***.***> wrote:
You must use 8080 to reach your ruTorrent interface, well :
- '127.0.0.1:8080:8080'
And
proxy_pass http://127.0.0.1:8080;
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0qzngXe-urSOnmHAWYQFc2Mv52GZWks5twBxqgaJpZM4T0kyf>.
|
|
Hi there,
I’ve edited my yml file which now looks like this :
rtorrent:
image: xataz/rtorrent-rutorrent
container_name: rtorrent
restart: always
network_mode: "bridge"
tty: true
ports:
- '127.0.0.1:45000:45000'
- '127.0.0.1:8080:8080'
- '127.0.0.1:6881:6881'
- '127.0.0.1:5000:5000'
environment:
- UID=1001
- GID=1001
- TZ=Europe/Paris
volumes:
- './rtorrent:/config'
- '/home/plexuser/downloads:/data'
Rutorrent is reachable, and connectes to Rtorrent. When I add a torrent file, it starts downloading the file. But I still get bad response from server errors, and it seems like files are not seeding after completion of the download. I see 0 peers connected.
Any idea what this could come from ?
Thanks again !
… On 7 May 2018, at 12:33, Raphael P ***@***.***> wrote:
Oh yes ! I did change my yml to :
rtorrent:
image: xataz/rtorrent-rutorrent
container_name: rtorrent
restart: always
network_mode: "bridge"
tty: true
ports:
- '127.0.0.1:45000:45000'
- '127.0.0.1:8080:8080'
environment:
- UID=1001
- GID=1001
- TZ=Europe/Paris
volumes:
- './rtorrent:/config'
- '/home/plexuser/downloads:/data’
and now I finally see rutorrent UI running ! thanks for that !
But now rutorrent still isn’t connected to the rtorrent running inside the container. I’m getting a bad response from server message. Bad response from server: (0 [error,list])
What am I supposed to do to fix this ? I see you did put a lot of ports in your run container example, therefore i’m a little bit confused (this is my first rtorrent/rutorrent install) :/
Thanks again !! I’m almost there ;)
> On 7 May 2018, at 12:05, Jérémy ***@***.*** ***@***.***>> wrote:
>
> You must use 8080 to reach your ruTorrent interface, well :
>
> - '127.0.0.1:8080:8080'
> And
>
> proxy_pass http://127.0.0.1:8080 <http://127.0.0.1:8080/>;
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0qzngXe-urSOnmHAWYQFc2Mv52GZWks5twBxqgaJpZM4T0kyf>.
>
|
|
FYI no error when logging in (so I guess rtorrent connexion is all set) , but after that, lots of different different errors :
… On 7 May 2018, at 13:53, Raphael P ***@***.***> wrote:
Hi there,
I’ve edited my yml file which now looks like this :
rtorrent:
image: xataz/rtorrent-rutorrent
container_name: rtorrent
restart: always
network_mode: "bridge"
tty: true
ports:
- '127.0.0.1:45000:45000'
- '127.0.0.1:8080:8080'
- '127.0.0.1:6881:6881'
- '127.0.0.1:5000:5000'
environment:
- UID=1001
- GID=1001
- TZ=Europe/Paris
volumes:
- './rtorrent:/config'
- '/home/plexuser/downloads:/data'
Rutorrent is reachable, and connectes to Rtorrent. When I add a torrent file, it starts downloading the file. But I still get bad response from server errors, and it seems like files are not seeding after completion of the download. I see 0 peers connected.
Any idea what this could come from ?
Thanks again !
> On 7 May 2018, at 12:33, Raphael P ***@***.*** ***@***.***>> wrote:
>
> Oh yes ! I did change my yml to :
>
> rtorrent:
> image: xataz/rtorrent-rutorrent
> container_name: rtorrent
> restart: always
> network_mode: "bridge"
> tty: true
> ports:
> - '127.0.0.1:45000:45000'
> - '127.0.0.1:8080:8080'
> environment:
> - UID=1001
> - GID=1001
> - TZ=Europe/Paris
> volumes:
> - './rtorrent:/config'
> - '/home/plexuser/downloads:/data’
>
> and now I finally see rutorrent UI running ! thanks for that !
>
> But now rutorrent still isn’t connected to the rtorrent running inside the container. I’m getting a bad response from server message. Bad response from server: (0 [error,list])
>
>
> What am I supposed to do to fix this ? I see you did put a lot of ports in your run container example, therefore i’m a little bit confused (this is my first rtorrent/rutorrent install) :/
>
> Thanks again !! I’m almost there ;)
>
>
>> On 7 May 2018, at 12:05, Jérémy ***@***.*** ***@***.***>> wrote:
>>
>> You must use 8080 to reach your ruTorrent interface, well :
>>
>> - '127.0.0.1:8080:8080'
>> And
>>
>> proxy_pass http://127.0.0.1:8080 <http://127.0.0.1:8080/>;
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0qzngXe-urSOnmHAWYQFc2Mv52GZWks5twBxqgaJpZM4T0kyf>.
>>
>
|
|
Hey there,
Just a litle update to let you know that opening listening ports helped me getting rid of the errors ;)
So I seem to be all set for now.
One more thing, how can I test if filebot is working ?
Best,
Me
… On 7 May 2018, at 13:59, Raphael P ***@***.***> wrote:
FYI no error when logging in (so I guess rtorrent connexion is all set) , but after that, lots of different different errors :
<PastedGraphic-1.png>
> On 7 May 2018, at 13:53, Raphael P ***@***.*** ***@***.***>> wrote:
>
> Hi there,
>
> I’ve edited my yml file which now looks like this :
>
> rtorrent:
> image: xataz/rtorrent-rutorrent
> container_name: rtorrent
> restart: always
> network_mode: "bridge"
> tty: true
> ports:
> - '127.0.0.1:45000:45000'
> - '127.0.0.1:8080:8080'
> - '127.0.0.1:6881:6881'
> - '127.0.0.1:5000:5000'
> environment:
> - UID=1001
> - GID=1001
> - TZ=Europe/Paris
> volumes:
> - './rtorrent:/config'
> - '/home/plexuser/downloads:/data'
>
> Rutorrent is reachable, and connectes to Rtorrent. When I add a torrent file, it starts downloading the file. But I still get bad response from server errors, and it seems like files are not seeding after completion of the download. I see 0 peers connected.
>
> Any idea what this could come from ?
>
> Thanks again !
>
>> On 7 May 2018, at 12:33, Raphael P ***@***.*** ***@***.***>> wrote:
>>
>> Oh yes ! I did change my yml to :
>>
>> rtorrent:
>> image: xataz/rtorrent-rutorrent
>> container_name: rtorrent
>> restart: always
>> network_mode: "bridge"
>> tty: true
>> ports:
>> - '127.0.0.1:45000:45000'
>> - '127.0.0.1:8080:8080'
>> environment:
>> - UID=1001
>> - GID=1001
>> - TZ=Europe/Paris
>> volumes:
>> - './rtorrent:/config'
>> - '/home/plexuser/downloads:/data’
>>
>> and now I finally see rutorrent UI running ! thanks for that !
>>
>> But now rutorrent still isn’t connected to the rtorrent running inside the container. I’m getting a bad response from server message. Bad response from server: (0 [error,list])
>>
>>
>> What am I supposed to do to fix this ? I see you did put a lot of ports in your run container example, therefore i’m a little bit confused (this is my first rtorrent/rutorrent install) :/
>>
>> Thanks again !! I’m almost there ;)
>>
>>
>>> On 7 May 2018, at 12:05, Jérémy ***@***.*** ***@***.***>> wrote:
>>>
>>> You must use 8080 to reach your ruTorrent interface, well :
>>>
>>> - '127.0.0.1:8080:8080'
>>> And
>>>
>>> proxy_pass http://127.0.0.1:8080 <http://127.0.0.1:8080/>;
>>> —
>>> You are receiving this because you authored the thread.
>>> Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0qzngXe-urSOnmHAWYQFc2Mv52GZWks5twBxqgaJpZM4T0kyf>.
>>>
>>
>
|
|
Lol, it cant works without the :filebot tag :-) (rtorrent-rutorrent:filebot)
|
|
AH. So I’m gonna change this
image: xataz/rtorrent-rutorrent
to this
image: xataz/rtorrent-rutorrent:filebot
and give it another shot ;)
Thanks !
… On 7 May 2018, at 14:26, Jérémy ***@***.***> wrote:
Lol, it cant works without the :filebot tag :-) (rtorrent-rutorrent:filebot)
Envoyé de mon iPhone
Le 7 mai 2018 à 14:11, silkyclouds ***@***.******@***.***>> a écrit :
Hey there,
Just a litle update to let you know that opening listening ports helped me getting rid of the errors ;)
So I seem to be all set for now.
One more thing, how can I test if filebot is working ?
Best,
Me
> On 7 May 2018, at 13:59, Raphael P ***@***.******@***.***>> wrote:
>
> FYI no error when logging in (so I guess rtorrent connexion is all set) , but after that, lots of different different errors :
>
> <PastedGraphic-1.png>
>
>
>> On 7 May 2018, at 13:53, Raphael P ***@***.******@***.***> ***@***.***>> wrote:
>>
>> Hi there,
>>
>> I’ve edited my yml file which now looks like this :
>>
>> rtorrent:
>> image: xataz/rtorrent-rutorrent
>> container_name: rtorrent
>> restart: always
>> network_mode: "bridge"
>> tty: true
>> ports:
>> - '127.0.0.1:45000:45000'
>> - '127.0.0.1:8080:8080'
>> - '127.0.0.1:6881:6881'
>> - '127.0.0.1:5000:5000'
>> environment:
>> - UID=1001
>> - GID=1001
>> - TZ=Europe/Paris
>> volumes:
>> - './rtorrent:/config'
>> - '/home/plexuser/downloads:/data'
>>
>> Rutorrent is reachable, and connectes to Rtorrent. When I add a torrent file, it starts downloading the file. But I still get bad response from server errors, and it seems like files are not seeding after completion of the download. I see 0 peers connected.
>>
>> Any idea what this could come from ?
>>
>> Thanks again !
>>
>>> On 7 May 2018, at 12:33, Raphael P ***@***.******@***.***> ***@***.***>> wrote:
>>>
>>> Oh yes ! I did change my yml to :
>>>
>>> rtorrent:
>>> image: xataz/rtorrent-rutorrent
>>> container_name: rtorrent
>>> restart: always
>>> network_mode: "bridge"
>>> tty: true
>>> ports:
>>> - '127.0.0.1:45000:45000'
>>> - '127.0.0.1:8080:8080'
>>> environment:
>>> - UID=1001
>>> - GID=1001
>>> - TZ=Europe/Paris
>>> volumes:
>>> - './rtorrent:/config'
>>> - '/home/plexuser/downloads:/data’
>>>
>>> and now I finally see rutorrent UI running ! thanks for that !
>>>
>>> But now rutorrent still isn’t connected to the rtorrent running inside the container. I’m getting a bad response from server message. Bad response from server: (0 [error,list])
>>>
>>>
>>> What am I supposed to do to fix this ? I see you did put a lot of ports in your run container example, therefore i’m a little bit confused (this is my first rtorrent/rutorrent install) :/
>>>
>>> Thanks again !! I’m almost there ;)
>>>
>>>
>>>> On 7 May 2018, at 12:05, Jérémy ***@***.******@***.***> ***@***.***>> wrote:
>>>>
>>>> You must use 8080 to reach your ruTorrent interface, well :
>>>>
>>>> - '127.0.0.1:8080:8080'
>>>> And
>>>>
>>>> proxy_pass http://127.0.0.1:8080 <http://127.0.0.1:8080/>;
>>>> —
>>>> You are receiving this because you authored the thread.
>>>> Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0qzngXe-urSOnmHAWYQFc2Mv52GZWks5twBxqgaJpZM4T0kyf>.
>>>>
>>>
>>
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#13 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACYYwZE1YzZ8v4uoCbOUzWM0ORT1xoaOks5twDmvgaJpZM4T0kyf>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0q_XHo-xbn7AkDTraRXe7tHhujDZYks5twD18gaJpZM4T0kyf>.
|
|
Hey there,
I’ve changed to rtorrent-rutorrent:filebot but still can’t see any filebot option in the rutorrent if.
I’m also getting a crazy load of errors
last but not least, I’ve mapped my volumes like that :
volumes:
- './rtorrent:/config'
- '/home/plexuser/downloads:/data'
rotrrent downloads files without any issue in /data/torrents, but can’t see any of the files that has been downloaded. Same issue with other content at the root of my downloads folder. As an example, I can NOT define I want to enable /data/watchfolder as my watchfolder.
any clue what I can do to fi all this ? :/
Thanks !
… On 7 May 2018, at 14:28, Raphael P ***@***.***> wrote:
AH. So I’m gonna change this
> image: xataz/rtorrent-rutorrent
to this
> image: xataz/rtorrent-rutorrent:filebot
and give it another shot ;)
Thanks !
> On 7 May 2018, at 14:26, Jérémy ***@***.*** ***@***.***>> wrote:
>
> Lol, it cant works without the :filebot tag :-) (rtorrent-rutorrent:filebot)
>
> Envoyé de mon iPhone
>
> Le 7 mai 2018 à 14:11, silkyclouds ***@***.*** ***@***.******@***.*** ***@***.***>>> a écrit :
>
> Hey there,
>
> Just a litle update to let you know that opening listening ports helped me getting rid of the errors ;)
>
> So I seem to be all set for now.
>
> One more thing, how can I test if filebot is working ?
>
> Best,
>
> Me
>
> > On 7 May 2018, at 13:59, Raphael P ***@***.*** ***@***.******@***.*** ***@***.***>>> wrote:
> >
> > FYI no error when logging in (so I guess rtorrent connexion is all set) , but after that, lots of different different errors :
> >
> > <PastedGraphic-1.png>
> >
> >
> >> On 7 May 2018, at 13:53, Raphael P ***@***.*** ***@***.******@***.*** ***@***.***>> ***@***.*** ***@***.***>>> wrote:
> >>
> >> Hi there,
> >>
> >> I’ve edited my yml file which now looks like this :
> >>
> >> rtorrent:
> >> image: xataz/rtorrent-rutorrent
> >> container_name: rtorrent
> >> restart: always
> >> network_mode: "bridge"
> >> tty: true
> >> ports:
> >> - '127.0.0.1:45000:45000'
> >> - '127.0.0.1:8080:8080'
> >> - '127.0.0.1:6881:6881'
> >> - '127.0.0.1:5000:5000'
> >> environment:
> >> - UID=1001
> >> - GID=1001
> >> - TZ=Europe/Paris
> >> volumes:
> >> - './rtorrent:/config'
> >> - '/home/plexuser/downloads:/data'
> >>
> >> Rutorrent is reachable, and connectes to Rtorrent. When I add a torrent file, it starts downloading the file. But I still get bad response from server errors, and it seems like files are not seeding after completion of the download. I see 0 peers connected.
> >>
> >> Any idea what this could come from ?
> >>
> >> Thanks again !
> >>
> >>> On 7 May 2018, at 12:33, Raphael P ***@***.*** ***@***.******@***.*** ***@***.***>> ***@***.*** ***@***.***>>> wrote:
> >>>
> >>> Oh yes ! I did change my yml to :
> >>>
> >>> rtorrent:
> >>> image: xataz/rtorrent-rutorrent
> >>> container_name: rtorrent
> >>> restart: always
> >>> network_mode: "bridge"
> >>> tty: true
> >>> ports:
> >>> - '127.0.0.1:45000:45000'
> >>> - '127.0.0.1:8080:8080'
> >>> environment:
> >>> - UID=1001
> >>> - GID=1001
> >>> - TZ=Europe/Paris
> >>> volumes:
> >>> - './rtorrent:/config'
> >>> - '/home/plexuser/downloads:/data’
> >>>
> >>> and now I finally see rutorrent UI running ! thanks for that !
> >>>
> >>> But now rutorrent still isn’t connected to the rtorrent running inside the container. I’m getting a bad response from server message. Bad response from server: (0 [error,list])
> >>>
> >>>
> >>> What am I supposed to do to fix this ? I see you did put a lot of ports in your run container example, therefore i’m a little bit confused (this is my first rtorrent/rutorrent install) :/
> >>>
> >>> Thanks again !! I’m almost there ;)
> >>>
> >>>
> >>>> On 7 May 2018, at 12:05, Jérémy ***@***.*** ***@***.******@***.*** ***@***.***>> ***@***.*** ***@***.***>>> wrote:
> >>>>
> >>>> You must use 8080 to reach your ruTorrent interface, well :
> >>>>
> >>>> - '127.0.0.1:8080:8080'
> >>>> And
> >>>>
> >>>> proxy_pass http://127.0.0.1:8080 <http://127.0.0.1:8080/> <http://127.0.0.1:8080/ <http://127.0.0.1:8080/>>;
> >>>> —
> >>>> You are receiving this because you authored the thread.
> >>>> Reply to this email directly, view it on GitHub <#13 (comment) <#13 (comment)>>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0qzngXe-urSOnmHAWYQFc2Mv52GZWks5twBxqgaJpZM4T0kyf <https://github.com/notifications/unsubscribe-auth/AWS0qzngXe-urSOnmHAWYQFc2Mv52GZWks5twBxqgaJpZM4T0kyf>>.
> >>>>
> >>>
> >>
> >
>
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub<#13 (comment) <#13 (comment)>>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACYYwZE1YzZ8v4uoCbOUzWM0ORT1xoaOks5twDmvgaJpZM4T0kyf <https://github.com/notifications/unsubscribe-auth/ACYYwZE1YzZ8v4uoCbOUzWM0ORT1xoaOks5twDmvgaJpZM4T0kyf>>.
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0q_XHo-xbn7AkDTraRXe7tHhujDZYks5twD18gaJpZM4T0kyf>.
>
|
|
Hello, I have other services exposing only ports and have but for some reason i have to map ip for torrent one (don't remember why now). And i am also reverse proxying everyting, just without SSL. |
|
thanks for your help Justas !
Unfortunately it doesn’t solve my issues. :(
When adding the FILEBOT params in environment I get these errors :
ERROR: Invalid interpolation format for "environment" option in service "rtorrent": "FILEBOT_RENAME_SERIES="{n}/Season {s.pad(2)}/{n} - {s00e00} - {t$”"
Regarding the volumes, rtorrent do see and create the config files without any issue.
rtorrent downloads in /data/torrents without any issue.
in file manager, I can see the content of /data/torrents but for some reason, I can not browse to the upper folder which contains my watchfolder.
I’m also not able to move my files manually by selecting any other folder. This is really strange.
In the end, my only wish is to :
1. download the file in my /data/torrent folder
2. once downloaded, filebot renames and COPIES the renamed file to my movie / serie location which is located on another drive /medias/Plex/movies and /medias/Plex/series
3. the downloaded torrent stays in its initial location /data/torrents and keeps seeding
no rocket science but for some reasons i’m stuck… :/
… On 11 May 2018, at 06:06, Justas Stankūnas ***@***.***> wrote:
Hello,
Not sure if this helps but here is torrent part from my yml file:
torrent:
image: xataz/rtorrent-rutorrent:latest-filebot
restart: unless-stopped
container_name: torrent
volumes:
- /mnt/md0/system/containers/mediaserver/torrent/config:/config
- /mnt/md0/system/containers/mediaserver/torrent/data:/data
- /mnt/md0/media-library:/data/Media
environment:
FILEBOT_RENAME_METHOD: duplicate
WEBROOT: "/torrent"
FILEBOT_RENAME_MOVIES: "{n} ({y})/{n}"
FILEBOT_RENAME_SERIES: "{n}/Season {s.pad(2)}/{n} - {s00e00} - {t$
UID: 1005
GID: 10000
ports:
- "192.168.11.101:8080:8080"
I have other services exposing only ports and have but for some reason i have to map ip for torrent one (don't remember why now). And i am also reverse proxying everyting, just without SSL.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0q26F2u2iI8kN8xa9vVg0vj3OSoJeks5txQ5igaJpZM4T0kyf>.
|
|
Hi guys,
I’ve managed to have my Media folder containing my movies (located on a Gdrive) mounted and visible inside rutorrent UI.
now I am able to make a “save as…” and move a movie to my google drive mount. which means I could be able now to tell rtorrent to execute filebot at the end of a download in order to copy the renamed file to that same google drive mount point.
My last question would therefore be, how can I achieve this ? Do I have to create a rtorrent_postprocess file as I did see in some tutorials? Or how is this working inside your container xataz ?
I actually want to COPY (and keep the initial file unchanged so it seeds) the renamed file inside /data/torrent/Media/medias/movies/ when the dl is finished.
Can anyone let me know how to do this ? I’m really at the last step of this whole setup and would like to get this done once for all.
Thank you !!!
… On 11 May 2018, at 12:50, Raphael P ***@***.***> wrote:
thanks for your help Justas !
Unfortunately it doesn’t solve my issues. :(
When adding the FILEBOT params in environment I get these errors :
ERROR: Invalid interpolation format for "environment" option in service "rtorrent": "FILEBOT_RENAME_SERIES="{n}/Season {s.pad(2)}/{n} - {s00e00} - {t$”"
Regarding the volumes, rtorrent do see and create the config files without any issue.
rtorrent downloads in /data/torrents without any issue.
in file manager, I can see the content of /data/torrents but for some reason, I can not browse to the upper folder which contains my watchfolder.
I’m also not able to move my files manually by selecting any other folder. This is really strange.
In the end, my only wish is to :
1. download the file in my /data/torrent folder
2. once downloaded, filebot renames and COPIES the renamed file to my movie / serie location which is located on another drive /medias/Plex/movies and /medias/Plex/series
3. the downloaded torrent stays in its initial location /data/torrents and keeps seeding
no rocket science but for some reasons i’m stuck… :/
> On 11 May 2018, at 06:06, Justas Stankūnas ***@***.*** ***@***.***>> wrote:
>
> Hello,
> Not sure if this helps but here is torrent part from my yml file:
>
> torrent:
> image: xataz/rtorrent-rutorrent:latest-filebot
> restart: unless-stopped
> container_name: torrent
> volumes:
> - /mnt/md0/system/containers/mediaserver/torrent/config:/config
> - /mnt/md0/system/containers/mediaserver/torrent/data:/data
> - /mnt/md0/media-library:/data/Media
> environment:
> FILEBOT_RENAME_METHOD: duplicate
> WEBROOT: "/torrent"
> FILEBOT_RENAME_MOVIES: "{n} ({y})/{n}"
> FILEBOT_RENAME_SERIES: "{n}/Season {s.pad(2)}/{n} - {s00e00} - {t$
> UID: 1005
> GID: 10000
> ports:
> - "192.168.11.101:8080:8080"
> I have other services exposing only ports and have but for some reason i have to map ip for torrent one (don't remember why now). And i am also reverse proxying everyting, just without SSL.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWS0q26F2u2iI8kN8xa9vVg0vj3OSoJeks5txQ5igaJpZM4T0kyf>.
>
|
|
@silkyclouds second of that. this container will move or copy (duplicate) your media to /data/Media inside it. so what ever you will map to this directory media will be placed there (i am mounting there already existing media directory on my server - /mnt/md0/media-library:/data/Media) and WEBROOT i am using to make it easier to reverse proxy web UI. |
|
Hey there,
thanks again for your nice and clear explanations.
here is how my rtorrent section looks like in my docker-compose.yml :
rtorrent:
image: xataz/rtorrent-rutorrent:latest-filebot
container_name: rtorrent
restart: always
network_mode: "bridge"
tty: true
ports:
- '45000:45000'
- '127.0.0.1:8080:8080'
- '127.0.0.1:6881:6881'
- '127.0.0.1:5000:5000'
environment:
FILEBOT_RENAME_METHOD: duplicate
FILEBOT_RENAME_MOVIES: "{n} ({y})/{n}"
FILEBOT_RENAME_SERIES: "{n}/Season {s.pad(2)}/{n} - {s00e00} - {t}"
UID: 1001
GID: 1001
volumes:
- '/home/plexuser/.config/rtorrent:/config'
- '/home/plexuser/downloads:/data'
- '/home/plexuser/downloads/torrents/Media/medias:/data/Media’
And it just works when I do a docker-compose pull and docker-compose up -d
Now rtorrent is running. I’ll add a movie to see if Filebot does it’s job.
so from now on my movies should be automatically renamed and duplicated in /data/Media/Movie name (year)/moviename.filetype is that right ?
Is there any way to check the filebot logs specifically running inside the docker container ?
thanks again !!!
… On 14 May 2018, at 08:28, Justas Stankūnas ***@***.***> wrote:
FILEBOT_RENAME_METHOD: duplicate
WEBROOT: "/torrent"
FILEBOT_RENAME_MOVIES: "{n} ({y})/{n}"
FILEBOT_RENAME_SERIES: "{n}/Season {s.pad(2)}/{n} - {s00e00} - {t}"
|
|
yes, in theory it should work and you should see them in /home/plexuser/downloads/torrents/Media/medias :) for the logs, try this command from server you are running docker on: |
|
It works! Thank you so much for helping me out!
… Le 14 mai 2018 à 15:21, Justas Stankūnas ***@***.***> a écrit :
try this command from server you are running docker on:
docker exec -it rtorrent cat /filebot/data/logs/amc.log
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
Would some nice person post a yml file in order to let me install this using docker-compose ?
that would be really nice !
Thanks !
The text was updated successfully, but these errors were encountered: