Skip to content


Jellyfin is best described as "like Emby but really FOSS".

Jellyfin Screenshot

If it looks very similar as Emby, is because it started as a fork of it, but it has evolve since them. For a complete explanation of the why, look here.


  1. Docker swarm cluster with persistent shared storage
  2. Traefik configured per design
  3. DNS entry for the hostname you intend to use, pointed to your keepalived IP


Setup data locations

We'll need a location to store Jellyfin's library data, config files, logs and temporary transcoding space, so create /var/data/jellyfin, and make sure it's owned by the user and group who also own your media data.

mkdir /var/data/jellyfin

Also if we want to avoid the cache to be part of the backup, we should create a location to map it on the runtime folder. It also has to be owned by the user and group who also own your media data.

mkdir /var/data/runtime/jellyfin

Prepare environment

Create jellyfin.env, and populate with PUID/GUID for the user who owns the /var/data/jellyfin directory (above) and your actual media content (in this example, the media content is at /srv/data)


Setup Docker Swarm

Create a docker swarm config file in docker-compose syntax (v3), something like this:


I share (with my sponsors) a private "premix" git repository, which includes necessary docker-compose and env files for all published recipes. This means that sponsors can launch any recipe with just a git pull and a docker stack deploy 👍

version: "3.0"

    image: jellyfin/jellyfin
    env_file: /var/data/config/jellyfin/jellyfin.env
      - /etc/localtime:/etc/localtime:ro
      - /var/data/jellyfin:/config
      - /var/data/runtime/jellyfin:/cache
      - /var/data/jellyfin/jellyfin:/config
      - /srv/data/:/data
        - traefik.port=8096
        - traefik_public
        - internal
      - 8096:8096

    external: true
    driver: overlay
        - subnet:


Setup unique static subnets for every stack you deploy. This avoids IP/gateway conflicts which can otherwise occur when you're creating/removing stacks a lot. See my list here.


Launch Jellyfin stack

Launch the stack by running docker stack deploy jellyfin -c <path -to-docker-compose.yml>

Log into your new instance at https://YOUR-FQDN, and complete the wizard-based setup to complete deploying your Jellyfin.

Chef's Notes 📓

  1. I didn't use an oauth2_proxy for this stack, because it would interfere with mobile client support.
  2. Got an NVIDIA GPU? See this blog post re how to use your GPU to transcode your media!
  3. We don't bother exposing the HTTPS port for Jellyfin, since Traefik is doing the SSL termination for us already.

Tip your waiter (sponsor me) 👏

Did you receive excellent service? Want to make your waiter happy? (..and support development of current and future recipes!) Sponsor me on Github / Patreon, or see the support page for more (free or paid) ways to say thank you! 👏

Flirt with waiter (subscribe) 💌

Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated. (*double-opt-in, no monkey business, no spam)

Notify me 🔔

Be the first to know when recipes are added / improved!

    We won't send you spam. Unsubscribe at any time. No monkey-business.

    Powered By ConvertKit

    Your comments? 💬

    Last update: August 6, 2020