2025-02-21, 03:42 PM
You cannot import your bare metal linux install into a docker install without significant configuration changes. Jellyfin uses a lot of absolute paths for metadata files and images. The migration document specifics how you modify docker to trick it into using the existing data from the bare metal install.
But those paths don't exist in your unRAID setup. The migration document assumes you are not migrating to a different OS or different machine entirely. It assumes you are staying on the same host and same OS, but switching to running Jellyfin in Docker vs a system service.
You'd have to do ADDITIONAL configuration in unRAID to create those paths and then map additional paths in unRAID to match how Jellyfin's data would arranged in a bare metal install.
/host/volume/jellyfin/etc
etc/jellyfin
/host/volume/jellyfin/varlib
var/lib/jellyfin
/host/volume/jellyfin/varcache
var/cache/jellyfin
/host/volume/jellyfin/varlog
var/log/jellyfin
Something like that. Then you modify the docker environment variables for the data directory, cache directory, etc., to use those directories instead of the docker defaults in "/config" and "/cache".
But those paths don't exist in your unRAID setup. The migration document assumes you are not migrating to a different OS or different machine entirely. It assumes you are staying on the same host and same OS, but switching to running Jellyfin in Docker vs a system service.
You'd have to do ADDITIONAL configuration in unRAID to create those paths and then map additional paths in unRAID to match how Jellyfin's data would arranged in a bare metal install.
/host/volume/jellyfin/etc

/host/volume/jellyfin/varlib

/host/volume/jellyfin/varcache

/host/volume/jellyfin/varlog

Something like that. Then you modify the docker environment variables for the data directory, cache directory, etc., to use those directories instead of the docker defaults in "/config" and "/cache".