SOLVED: Transferring Jellyfin from HTPC to ITX build

[Deleted User]

if it's in docker going to a docker then it is simpler than you might think

if everything is setup nominally and you use portainer -

in the current docker, edit libraries and turn off real time monitoring, important in case things do not line up jellyfin will not scan bad paths

in your current docker you have paths to media and a path to /config in the container, these are pretty much all you need to duplicate to a new docker

on the omv host make a backup of the path /config points to

on the new system setup a new instance of jellyfin, i use the cli from here - https://hub.docker.com/r/linuxserver/jellyfin

once setup you just need to restore your paths in the container for media and restore the config backup

if you amend the cli with the correct paths using multiple -v (for volume) your paths will be setup in the container
- or you can add them later with portainer

just be sure the container paths match the original, the host paths are not important

if everything goes well, it will be up and running

if somehow you did not use the same uid:gid you will need to chown the files to the new uid:gid

if it goes wrong, shutdown the docker and re-import the backup config as many times as you wish

to make the backup of config, tar or simply cp -a as they will both preserve uid:gid

re-enable real time monitoring after everything is up in the new container