Why do I have a separate Jackett docker image every day?!
Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining gifs, inspiring stories, viral videos, and so much more from users.
You're viewing a single thread.
Real question is, why Jackett instead of Prowlarr? 😄
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.
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 😆
Prowlarr's "guide" for docker implementation is scary
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:
nix
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...
Never had an issue. But I installed them all using my distro package manager, so no hassle with volumes and links.
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.
Yes - but I have no idea about docker, sorry. Have it running baremetal (or rather, in a proxmox VM).
Just a hunch, but in case you "only" share the directory where Sonarr puts Episode files with Jellyfin via some mount point or whatever, and not the directory where Sonarr gets them from (where the torrent client downloads to), then I can see hardlinks breaking in unexpected ways
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 😁
Just found this. https://lemm.ee/post/58579926
Seems like I'm not so weird after all....
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
services:
gluetun:
image: qmcgaw/gluetun
container_name: gluetun
cap_add:
- NET_ADMIN
environment:
- DNS_ADDRESS=
- PUID=1000
- PGID=1000
- SERVER_CITIES=
- FIREWALL_VPN_INPUT_PORTS=
- TZ=Etc/UTC
# Provider readmes: https://github.com/qdm12/gluetun-wiki/tree/main/setup/providers
- VPN_SERVICE_PROVIDER=
#- VPN_TYPE=openvpn
#- OPENVPN_CUSTOM_CONFIG=/config/custom.conf
#- VPN_TYPE=wireguard
#- WIREGUARD_PRIVATE_KEY=
#- WIREGUARD_ADDRESSES=
ports:
- 6767:6767 # bazaar
- 7878:7878 # radaar
- 8118:8118 # privoxy
- 8191:8191 # flaresolverr
- 8787:8787 # readaar
- 8989:8989 # sonaar
- 9091:9091 # transmission
- 9696:9696 # prowlarr
# You can add an forwarded listening ports your VPN provider might have here as well.
volumes:
- /data/gluetun:/config
bazarr:
image: lscr.io/linuxserver/bazarr:latest
container_name: bazarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/bazarr:/config
- /share/downloads/movies:/share/downloads/movies
- /share/downloads/tv:/share/downloads/tv
restart: unless-stopped
network_mode: service:gluetun
flaresolverr:
# DockerHub mirror flaresolverr/flaresolverr:latest
image: ghcr.io/flaresolverr/flaresolverr:latest
container_name: flaresolverr
environment:
- LOG_LEVEL=info
- LOG_HTML=false
- CAPTCHA_SOLVER=none
- TZ=Etc/UTC
restart: unless-stopped
network_mode: service:gluetun
privoxy:
image: caligari/privoxy:latest
container_name: privoxy
restart: unless-stopped
network_mode: service:gluetun
prowlarr:
image: lscr.io/linuxserver/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/prowlarr:/config
restart: unless-stopped
network_mode: service:gluetun
radarr:
image: lscr.io/linuxserver/radarr:latest
container_name: radarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/radarr:/config
- /share/downloads/movies:/share/downloads/movies
restart: unless-stopped
network_mode: service:gluetun
readarr:
image: lscr.io/linuxserver/readarr:develop
container_name: readarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/readarr:/config
- /share/downloads/books:/share/downloads/books
restart: unless-stopped
network_mode: service:gluetun
sonarr:
image: lscr.io/linuxserver/sonarr:latest
container_name: sonarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/sonarr:/config
- /share/downloads/tv:/share/downloads/tv
restart: unless-stopped
network_mode: service:gluetun
transmission:
image: lscr.io/linuxserver/transmission:latest
container_name: transmission
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- TRANSMISSION_WEB_HOME= #optional
- USER= #optional
- PASS= #optional
- WHITELIST= #optional
- PEERPORT= #optional
- HOST_WHITELIST= #optional
volumes:
- /data/transmission:/config
- /share/downloads/movies:/share/downloads/movies
- /share/downloads/books:/share/downloads/books
- /share/downloads/tv:/share/downloads/tv
restart: unless-stopped
network_mode: service:gluetun
watchtower:
container_name: watchtower
image: containrrr/watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
network_mode: service:gluetun
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.
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.
it's those pesky docker volume maps and hardlinks
Check out Trash Guides
I'm not the OP, but it's a headache even with trash guides
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