Real question is, why Jackett instead of Prowlarr? π
this post was submitted on 16 Mar 2025
41 points (100.0% liked)
Selfhosted
58814 readers
345 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (donβt cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Dunno, man. Its been working so far. I'll check out prowlarr, thanks
Yeah no worries - I discovered Prowlarr from that exact same comment years ago so jumped at the opportunity to post it here π
Tbh the whole arr suite is a headache to get working well...
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?
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.
I have them all running in a docker compose, that also has gluetun as the gateway.
It's a real basic compse file, but I can share it if you like.
Sure, why not? I'm setting up my new server, so no better time. Thanks
You might also want to check out https://yams.media/, it's pretty much an install script and configuration walkthrough that's very complete and detailed. Includes most relevant Arrs and gluetun builtin. Containerized. Choice of Emby, Plex or Jellyfin.
Prowlarr, recyclarr, and trash guides.
it's those pesky docker volume maps and hardlinks
Whatβs not working for you?
For me after a decade using -arr the only thing Iβve had significant issues with has been trying to use the Tailscale integration on Unraid 7 to tunnel the dockers through an exit node which isβ¦ not at all the fault of -arr containers lol
I've had the opposite experience. It all "just worked". Try running unraid. It makes a lot of it so much easier.
It's* been working
Looking at linuxserver/jackett on Docker Hub, it seems it indeed update everyday.
I'm not receiving daily updates from my gotify server, where watchtower reports the updates. But I guess it makes sense if it has some sort of automated build process. I've added the environment variable not to be updated by watchtower and I will keep an eye on it.
You can also tell watchtower to cleanup images after update so you don't end up with all of those old ones.
Interesting
If you're just pulling "latest" then docker will fetch the latest when it starts. You can pin to a version tag if you want to keep it stable.
docker image prune
Presumably because it updates daily
I thought so but my watchtower says "no".
I believe Linux Server builds images every day for most of their containers, even though there has been no code changes.
If the code doesn't change, the resulting docker image will have the same hash, and a new image won't be created
https://github.com/jackett/jackett/releases
Jackett is literally just releasing a new version every day