.. | ||
readme.md |
Jellyfin in docker
guide-by-example
Purpose & Overview
WORK IN PROGRESS
WORK IN PROGRESS
WORK IN PROGRESS
Stream movies/tv-shows/music to a browser, or a large selection of devices and services.
Jellyfin if a free media system, an alternative to proprietary Plex.
The core server side is written in C#, web client in Javascript,
and a number of other clients written in various languages and frameworks.
Starting point for me was this viggy96 repo
Files and directory structure
/mnt/
└── bigdisk/
├── tv/
├── movies/
└── music/
/home/
└── ~/
└── docker/
└── jellyfin/
├── jellyfin-cache/
├── jellyfin-config/
├── transcodes/
├── .env
└── docker-compose.yml
/mnt/bigdisk/...
- a mounted media storage sharejellyfin-cache/
- cachejellyfin-config/
- configurationtranscodes/
- transcoded video storage.env
- a file containing environment variables for docker composedocker-compose.yml
- a docker compose file, telling docker how to run the containers
You only need to provide the two files.
The directories are created by docker compose on the first run.
docker-compose
The media are mounted in read only mode.
docker-compose.yml
services:
jellyfin:
image: jellyfin/jellyfin:latest
container_name: jellyfin
hostname: jellyfin
restart: unless-stopped
env_file: .env
devices:
- /dev/dri
volumes:
- ./transcodes/:/transcodes
- ./jellyfin-config:/config
- ./jellyfin-cache:/cache
- /mnt/bigdisk/serialy:/media/video:ro
- /mnt/bigdisk/mp3/moje:/media/music:ro
ports:
- "8096:8096"
- "1900:1900/udp"
networks:
default:
name: $DOCKER_MY_NETWORK
external: true
.env
# GENERAL
DOCKER_MY_NETWORK=caddy_net
TZ=Europe/Bratislava
All containers must be on the same network.
Which is named in the .env
file.
If one does not exist yet: docker network create caddy_net
Reverse proxy
Caddy is used, details
here.
Caddyfile
jellyfin.{$MY_DOMAIN} {
reverse_proxy jellyfin:8096
}
First run
Specifics of my setup
-
no long term use yet
-
amd cpu and no gpu, so no experience with hw transcoding
-
media files are stored and shared on trunas scale VM and mounted directly on the docker host using systemd mounts, instead of fstab or autofs.
/etc/systemd/system/mnt-bigdisk.mount
[Unit] Description=12TB truenas mount [Mount] What=//10.0.19.19/Dataset-01 Where=/mnt/bigdisk Type=cifs Options=ro,username=ja,password=qq,file_mode=0700,dir_mode=0700,uid=1000 DirectoryMode=0700 [Install] WantedBy=multi-user.target
/etc/systemd/system/mnt-bigdisk.automount
[Unit] Description=12TB truenas mount [Automount] Where=/mnt/bigdisk [Install] WantedBy=multi-user.target
to automount on boot -
sudo systemctl enable mnt-bigdisk.automount
Troubleshooting
We're unable to connect to the selected server right now. Please ensure it is running and try again.
If you encounter this, try opening the url in browsers private window.
If it works then clear the cookies in your browser.
Update
Manual image update:
docker-compose pull
docker-compose up -d
docker image prune
Backup and restore
Backup
Using borg that makes daily snapshot of the entire directory.
Restore
- down the bookstack containers
docker-compose down
- delete the entire bookstack directory
- from the backup copy back the bookstack directory
- start the containers
docker-compose up -d