Thanks to this community popping up on my hot feed, I’ve spent my entire day setting up sonarr/radarr on my 423+ NAS within docker. I got most of it figured out on my own but I’m stumped on how sonarr/radarr takes the files from my torrent client downloads folder and moves them to my media folder for plex/jellyfin to view.
I’ve followed this guide for how my folder structure is setup: https://wiki.servarr.com/docker-guide
Could someone point me in the direction of what I need to do so that when a file is finished downloading it automatically moves to my media folder?
I am using transmission but I am open to any of them I can get to work correctly. So with how you have Deluge set up, Sonarr takes your files from the downloads folder and moves them a different media folder that Plex, Jellyfin, etc. can view?
Actually, the files don’t get moved by default. The are hardlinked. That means the files are accessible from both the original downloads location (for seeding) and in the location you made Sonarr/Radarr save them too, but only take space on the disk once.
I have a setup with transmission working, I can link you my config, but it’s in Nix.
I basically made Sonarr, Radarr, etc. all part of a group called
arr, and made all the folders with media have permissions that allow the group to read and write to them, and it works so far. I think.I’m not sure you even need to go that far. I’ll have to look up exactly how I have it configured because it’s been a bit, but sonarr and radarr are both configured to copy from the torrent folder into a separate media directory where they and Jellyfin, as part of the “media” group, have (almost) full permissions to manage the files as they like. Then I go in and occasionally prune the torrents folder once every few weeks if storage becomes an issue.
Mine aren’t hard linked then because radarr is copying them from my /data/torrents (qbittorrent download location) and putting them in my /data/media/movies folder. When I view the properties of the top level folder it is showing the space used as twice what the actual file is.
That should be a simple setting in both radarr and sonarr. They can hardlink or copy. I’m not sure what the default is nowadays but it was copy when I installed it.
The hard linking only works of the source and destination are in the same mount, for example
/data/downloads:/downloads /data/media:/mediaWill create copies and use double the storage on just hard linking, to make it hardlink you need to put the downloads and destination folders in the same directory so make the docker mount look like/data:/datainstead. Then you just need to tell your torrent client to put the downloaded files into /data/downloads/(either sonarr or radarr) and the the arrs can look into their folders and then hardlink the files into /data/media/whateverI have no clue if any of this is understandable, but I can post my docker compose once I get to my pc
Yea, I have two volumes mounted to my container one for media and one for downloads. Media is mounted to all the *arrs and Plex, and downloads is mounted to deluge/sabnzbd and all the *arrs. I don’t think transmission supports labels, I am not sure. The ones that do support labels include qBittorrent and Deluge.
If you don’t have labels at all then sonarr and radarr will not know which items belong to them. Give a different one a try and set up labels and see if it works then.