US Trends

what do I need to change to switch to official jellfin image

To switch from a LinuxServer-style Jellyfin container to the official jellyfin/jellyfin image, the main thing you need to change is the config mount path. The official image stores its config in a config folder inside the container, while LinuxServer images often use a different internal layout, so reusing the same bind mount without adjustment usually breaks things.

What to change

  • Update your container image to jellyfin/jellyfin.
  • Change the volume mapping so your host config directory maps to the official container’s /config.
  • Keep your media and cache mounts pointed at their existing host folders if those are already working.
  • Make sure the container user has permission to read and write the config and media paths.

Example

If you were using something like this before:

yaml

image: linuxserver/jellyfin
volumes:
  - /path/to/config:/config
  - /path/to/media:/media

the key difference is usually not the host side, but whether your old LinuxServer config lived in the same structure as the official image expects. If it did not, you may need to copy or remap the files so the official container sees the Jellyfin config in /config.

Safe migration steps

  1. Stop the old container.
  2. Back up your current config folder.
  3. Switch the image name to the official one.
  4. Point the official container at /config.
  5. Start the container and verify permissions.
  6. If the server starts with an empty setup, copy the old config contents into the new config path and restart.

Permission check

Jellyfin’s docs recommend making sure the config directory is owned by the user the server runs as, because bad ownership is a common cause of startup issues. If needed, fix ownership on the host directory before restarting.

Practical note

For many users, the easiest path is to keep the same host config directory but verify that the contents are in the structure the official image expects. If your old setup came from LinuxServer and the data is laid out differently, copying the relevant files into the new /config mapping is the usual fix.