Skip to content
Velloreth
Tutorials 2 min read

Self-Host Jellyfin with Docker Compose: Your Private Netflix

Jellyfin plus Docker Compose gives you a private Netflix in an hour. Install, hardware transcoding, libraries, reverse proxy, and backups step by step.

By

Jellyfin searches hit 201K/month and grew 200% into 2026 for one reason: my data should stay with me. Fully open source, no tracking, no subscription, no account phoning home.

This gets you from empty server to private Netflix in about an hour.

What you need

NeedMinimumRecommended
HostAny x86_64/ARM64 with DockerIntel N100 mini-PC
OSUbuntu 24.04 / Debian 12Same with SSH + UFW
Docker28.x with Compose v2docker compose version is v2
Storage50 GB to test2 TB+ for real library
docker --version
docker compose version
sudo ufw allow OpenSSH
sudo ufw enable

The Compose file

services:
  jellyfin:
    image: jellyfin/jellyfin:10.10.3
    restart: unless-stopped
    user: "1000:1000"
    ports:
      - "127.0.0.1:8096:8096"
    volumes:
      - ./data/config:/config
      - ./data/cache:/cache
      - /mnt/media:/media:ro
    environment:
      - TZ=Asia/Kathmandu
    devices:
      - /dev/dri:/dev/dri

Bind media read-only so a bug cannot delete the library. Bind only localhost — Caddy will be the way in. Set user to your UID to avoid root-owned files.

Nvidia? Replace devices with runtime: nvidia plus NVIDIA_VISIBLE_DEVICES=all.

docker compose up -d --wait
ssh -L 8096:localhost:8096 user@server
# open http://localhost:8096

Name files correctly once and metadata just works: one folder per movie, shows as Show/Season 01/S01E01.mkv. Use /media container paths, not host paths.

Hardware transcoding

Dashboard > Playback > Transcoding. One 4K software transcode can pin a CPU; hardware makes it trivial.

GPUSetting
Intel iGPUVAAPI or QSV via /dev/dri
Nvidia GTX 1050+NVENC, proprietary drivers
AMD APUAMF / VAAPI, kernel 6.2+

Test with a 4K file forced to 1080p — GPU tool should show load, not htop at 400%.

Remote with Caddy

  proxy:
    image: caddy:2-alpine
    restart: unless-stopped
    ports: ["80:80", "443:443"]
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
      - caddy_data:/data
      - caddy_config:/config
volumes:
  caddy_data:
  caddy_config:
watch.example.com {
  reverse_proxy jellyfin:8096
}

Automatic HTTPS, no certbot cron. UFW allows only SSH, 80, 443.

Updates and backups

docker compose pull
docker compose up -d --wait
tar -czf "/backups/jellyfin-$(date +%F).tar.gz" -C jellyfin data/config

Media needs no container backup — it is already on disk. Restore is untar plus up -d. Test once before trusting it.

One server, one file, one proxy, one cron job. Nobody can remove your movies in January.

Frequently asked questions

Why Jellyfin instead of Plex?
Jellyfin is fully open source with no paywalled features or account requirement. Plex has slicker clients but needs an account and paywalls transcoding and offline features.
How much hardware does Jellyfin need?
Direct play needs almost nothing — a Pi 5 or old laptop works. Transcoding 4K needs hardware acceleration like Intel Quick Sync or Nvidia NVENC. One 4K software transcode can saturate a CPU.
Do I need a domain and reverse proxy?
Not for LAN-only use. For remote streaming, yes — Caddy gives automatic HTTPS with two lines and keeps you off raw port exposure.
Is self-hosting legal?
Jellyfin itself is legal open-source software. Only serve media you own or have rights to. Ripping discs for personal use varies by country — check local rules.