Open hamany99 opened 1 year ago
I assume the actual path /downloads/Media does not exist where autotorrent has access which makes this a docker path unalignment issue.
The path scan stuff works by asking rtorrent where the data is and rtorrent thinks it is in /downloads/.
Currently there is no real fix. I'm working on it in relation to #13 and a few other issues but I've been afraid of people making serious mistakes when they unalign paths in docker.
True regarding the path. I managed to resolve the docker path unalignment issue by adding an additional path to the docker similar to this suggestion: https://github.com/JohnDoee/autotorrent/issues/33#issuecomment-678794880
Currently, I've 2 ways to resolve this manually.
I'm open for suggestions.
Aligning the paths is never wrong but you might be best served by waiting for me to finish up the feature. It is the next thing I'll release.
I'm using rtorrent in a docker. Torrents added Manually have the path: (/downloads/Media/FOLDERNAME) Torrents added by autotorrent2 have the path: (/mnt/user/Media/FOLDERNAME)
When running "at2 ls", the script is only checking the torrents added by at2 script and ignores the ones added manually. Any way to overcome this issue and combine all torrents in one report?