So now that we’ve setup our arr-stack and are able to download stuff either via usenet or torrents we can actually set up something to consume our media on!
I’ve used Plex in the past and while it is a much more polished experience than jellyfin, the decisions made by the plex team are not really confidence inspiring when it comes to privacy. So i’ve switched over to jellyfin and i am more than happy with it!
Jellyseer on the other hand is a much more polished UI for Sonarr and Radarr. It connects to your jellyfin instance to chech what is available and it connects to your sonarr and radarr instance to tell them what you want to download. It’s super simple, has an integrated browser for all shows and movies for you to find and looks really frigging good. This is also amazing if you “offer your services” to friends and family, as this is a super easy to understand website for your other users to “request” shows and movies. You can configure if some users requests should automatically be approved or if you want to manually click yes and no for each request.
So let’s get going!
All these guides assume you have basic knowledge about docker & docker compose. To quickly summarize the methods here:
You either use a webui to manage your docker-compose like Dockge or you create a folder and a docker-compose.yaml for each service listed here and copy the contents of each of them into that docker-compose.yaml; IMPORTANT: You HAVE to name them docker-compose.yaml exactly like that. Do NOT name them radarr.yaml for example. After you created a docker-compose.yaml and filled it with the contents here, you simply run docker compose up -d
Since neither Jellyfin nor Jellyseer actually download some “problematic files” there is no need to run them through any VPN. Of course it doesn’t hurt to route them through the same VPN you have for sonarr / radarr and the likes.
I will provide two seperate docker-compose.yaml for the Jellyfin installation. One with hardware accelerated transcoding for NVidia cards, and one that has no hw-accel.
This is based entirely on my previous posts on how to set up your arr-stack (usenet or torrents. If you don’t use an arr-stack or already have one up and running with a different folder structure you’re on your own here.
Since we already established this folder structure we can simply add two more folders for jellyfin and jellyseer in the configs tree:
arr-stack (for this example let's say it's located in /mnt/arr-stack)
|---- media
|---- movies
|---- shows
|---- music
|---- etc.
|---- configs
|---- radarr
|---- sonarr
|---- qbittorrent
|---- jellyfin
|---- jellyseer
|---- etc.
|---- torrents
|---- complete
also, if you have a fast SSD in your system with enough free storage you can also create a folder there for your jellyfin cache. Let’s assume it is on /mnt/fastssd/jellyfin/cache This can make a drastic difference in performance and buffering.
services:
jellyfin:
image: jellyfin/jellyfin
container_name: jellyfin
user: 1000:1000
network_mode: host
volumes:
- /mnt/arr-stack:/mnt/arr-stack
- /mnt/arr-stack/configs/jellyfin:/config
- /mnt/fastssd/jellyfin/cache:/cache
restart: unless-stopped
services:
jellyfin:
image: jellyfin/jellyfin
container_name: jellyfin
user: 1000:1000
network_mode: host
volumes:
- /mnt/arr-stack:/mnt/arr-stack
- /mnt/arr-stack/configs/jellyfin:/config
- /mnt/fastssd/jellyfin/cache:/cache
restart: unless-stopped
extra_hosts:
- host.docker.internal:host-gateway
runtime: nvidia
deploy:
resources:
reservations:
devices:
- capabilities:
- gpu
To test if your server is properly configured to run docker containers with your NVidia GPU you can run the following command:
sudo docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi
This will open NVidia-SMI as a docker container. If you see a table there with information about your GPU and the power consumption etc. you’re good to go! If not, please look up how to configure your docker host for NVidia GPUs.
services:
jellyseerr:
image: fallenbagel/jellyseerr:latest
container_name: jellyseerr
environment:
- LOG_LEVEL=debug
- TZ=Europe/Berlin #Changethis to your timezone!
ports:
- 5055:5055
volumes:
- /mnt/arr-stack/configs/jellyseerr:/app/config
restart: unless-stopped
After we’ve started our services it’s time to open the webui’s and configure them.
Obviously this part only for if you set jellyfin up with your GPU.
This is the fundamental basic setup. Jellyfin has an extensive Plugin ecosystem for all different things to do. Most of them make it much more easy to get correct metadata for different types of content.
Now if you find a movie or show you can click on “Requst” and see that it will automatically push that request to either radarr or sonarr and they will start looking and downloading for it.
Now you also have a fully functional and possibly hardware accelerated Jellyfin instance that can do movies, shows and music.
One more interesting addition to this stack would be Jellystats
If you’re looking for something for adult content that goes hand in hand with Whisparr, look into stash and additionally xbvr if you’re looking for a VR library and player.
1. Posts must be related to the discussion of digital piracy
2. Don’t request invites, trade, sell, or self-promote
3. Don’t request or link to specific pirated titles, including DMs
4. Don’t submit low-quality posts, be entitled, or harass others
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
version:
property isobsolete, and you can safely remove those lines: https://github.com/compose-spec/compose-spec/blob/main/spec.md#version-top-level-element-obsoleteYou can also replace common or shared attributes between your configs using env files: https://docs.docker.com/compose/environment-variables/set-environment-variables/#use-the-env_file-attribute
Things I put there: UIDs, GIDs, TZ, shared mount paths, etc.
You’re right, but introducing .env files would be an extra step for each and every docker process here.
This was meant as an absolutely fundamental basic setup. If you know your way around docker you also know what to improve from those guides.
Everyone who does not know this, can get the services up and running without extra steps.
Nice heads up