Skip Navigation

Selfhosted @lemmy.world

flightyhobler @lemm.ee

2w ago

Why do I have a separate Jackett docker image every day?!

imgur.com

50 comments

Real question is, why Jackett instead of Prowlarr? 😄
- 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 😆
  
  It's* been working
- If i remember correctly, jackett allows you to add trackers that prowlarr doesn't have natively. Then you add jackett to prowlarr to distribute to the rest of your containers.

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.
  
  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
- Goodbye stopped containers.
  
  IIRC, a normal prune doesn't get rid of those, only the --all prune does that. The normal one only erases images that aren't associated with any container.

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

bro downloaded the mudroom closet and has a whole stack of jacketts

Do you have Kinsing? I just dealt with it this past week.

Laughs in nix

50 comments