There’s not really anything you need to configure host-side. Prowlarr needs to be able to communicate with sonarr and radarr (same as jackett), but otherwise it’s basically stateless.
Hell no, My downloads folder in my media folder are completely different. I copy everything from downloads to media It gets renamed, possibly resampled. The torrents are left in the original folder to seed unmolested.
Every once in a while I go through my torrent list and just tell the client to destroy the torrent and files for anything that I don’t care to seed anymore. Zero chance of it breaking my actual store.
There needs to be an overlap in the mount points of docker jellyfish and docker sonarr, etc. I don’t think I got it right. Besides, sonar ends up not moving the series inside the tv shows folder, leaving the episodes outside, in the media folder above. If I knew exactly what was going on I would fix it. Last time I dealt with it was ages ago, so perhaps I can do it now.
The over lap of docker containers needs to happen from inside the perspective of the container. If you send Radarr to pull a movie from bittorrent, they both need to “be in the same spot”. If bittorrent thinks it’s saving a movie to /data/torrent then Radarr also needs to see the movie at /data/torrent.
That’s why so many guides use the /data/ label scheme. Its just easy to use and implement. Side note, for hard links to work, all the folders need to be on the same drive. Can’t hard link between different drives.
Yeah no worries - I discovered Prowlarr from that exact same comment years ago so jumped at the opportunity to post it here 😆
Prowlarr’s “guide” for docker implementation is scary
This?
Nah, man. Check this out: https://prowlarr.com/#downloads-v3-other
Neither option makes me feel confident.
I am a bit confused tbh 😅
The link you send links to docker projects, the link I sent is the second one of those. Seems pretty straightforward?
But to be fair, I have never used docker for any of this. In my nix config, it’s literally just:
services.prowlarr.enable = true; services.prowlarr.openFirewall = true;There’s not really anything you need to configure host-side. Prowlarr needs to be able to communicate with sonarr and radarr (same as jackett), but otherwise it’s basically stateless.
You might be right. Last time I checked I was still a bit “green” with this. It’s been two years and I think it makes more sense now 😉
The main issue is that for the prowler developers it seems like none of the docker options is ideal…
Tbh the whole arr suite is a headache to get working well…
https://trash-guides.info/
Never had an issue. But I installed them all using my distro package manager, so no hassle with volumes and links.
Prowlarr, recyclarr, and trash guides.
I tried recyclearr but found configarr to be more flexible.
https://github.com/raydak-labs/configarr/
Here is my configarr config:https://github.com/raldone01/configarr_config
I believe configarr is just a superset of recyclearr.
Sorry to hear that that’s been your experience! :( My installation has been running for ~5 years without any problems
you got the hard links working?
Hell no, My downloads folder in my media folder are completely different. I copy everything from downloads to media It gets renamed, possibly resampled. The torrents are left in the original folder to seed unmolested.
Every once in a while I go through my torrent list and just tell the client to destroy the torrent and files for anything that I don’t care to seed anymore. Zero chance of it breaking my actual store.
Hard links are a built-in feature of basically every modern filesystem. The bigger question to me is, why aren’t hard links working for you?
There needs to be an overlap in the mount points of docker jellyfish and docker sonarr, etc. I don’t think I got it right. Besides, sonar ends up not moving the series inside the tv shows folder, leaving the episodes outside, in the media folder above. If I knew exactly what was going on I would fix it. Last time I dealt with it was ages ago, so perhaps I can do it now.
The over lap of docker containers needs to happen from inside the perspective of the container. If you send Radarr to pull a movie from bittorrent, they both need to “be in the same spot”. If bittorrent thinks it’s saving a movie to /data/torrent then Radarr also needs to see the movie at /data/torrent.
That’s why so many guides use the /data/ label scheme. Its just easy to use and implement. Side note, for hard links to work, all the folders need to be on the same drive. Can’t hard link between different drives.
This was the crux of my confusion, but after a couple of years of Docker, it now makes more sense to me 😁