Migrate jellyfin package to docker container on Synology NAS

[DitchPickle24]

I am currently running the community jellyfin package on my Synology NAS, but would like to switch over to the official jellyfin docker image. I've seen some guides to move from PC to docker, and Plex synology package to a plex docker container, but have not been able to find any info on migrating this type of jellyfin installation.
Does anyone know of a way to make this migration, or at minimum, tranfer user logins?

[TheDreadPirate]

My understanding is that the Synology community package is just a re-wrap of our docker image. So it should be as simple as finding where your "/config" Jellyfin directory is stored on your Synology file system and pointing the standard Docker instance of our image at it.

I don't have a Synology NAS so I can't really help you figure the specifics of where to look.

BUT, it is also possible that they've made some changes to how their version works and it isn't directly compatible with a vanilla docker Jellyfin. For example, the /config folder for a LSIO Jellyfin Docker instance CANNOT be reused with the official Jellyfin Docker. Something about differences in where config files are located.

[bigdrock44]

I am currently running the community jellyfin package on my Synology NAS, but would like to switch over to the official jellyfin docker image. I've seen some guides to move from PC to docker, and Plex synology package to a plex docker container, but have not been able to find any info on migrating this type of jellyfin installation.
Does anyone know of a way to make this migration, or at minimum, tranfer user logins?

Did you manage to figure this out? I'm going through the same thing now and getting a little hung up, especially when it comes to locating the existing config file

[Haxornator]

I am currently running the community jellyfin package on my Synology NAS, but would like to switch over to the official jellyfin docker image. I've seen some guides to move from PC to docker, and Plex synology package to a plex docker container, but have not been able to find any info on migrating this type of jellyfin installation.
Does anyone know of a way to make this migration, or at minimum, tranfer user logins?

Did you manage to figure this out? I'm going through the same thing now and getting a little hung up, especially when it comes to locating the existing config file

Anyone have any luck on this?
I want to migrate so I can finally have HW transcoding.

[Anon]

I need to do this as well now, I was great greatly appreciate a guide of any kind on how to do this process / if it's possible.

[Efficient_Good_5784]

As @TheDreadPirate stated earlier in this thread, all you have to do is find the config folder on the system. You then copy it and paste it into an accesible location on your server.

When that's done, you just link it to the new Jellyfin container with a host mount.

The only thing we can't guarantee is that Synology community package for Jellyfin has any modifications that would prevent it from working right with Jellyfin's official image. You'll have to ask around for people that have experience with it for that answer. Or you could test it out yourself to see if it works fine.

[kandykarter]

I haven't run Jellyfin on my DS220+ in a while so this information might be outdated.

The Jellyfin community package stored data in /volume1/@appdata/jellyfin/.

I am unable to access that directory from the DSM's internal file browser, but I was able to find it using the File Browser app. If it were me, I'd stop my Jellyfin server, and use File Browser to copy the /volume1/@appdata/jellyfin/ into your docker config folder, and then point your docker to that folder.

Let me know if you need any further info, while I'm not running Jellyfin on my synology anymore, I still have the config files for it.

[Anon]

Thanks guys, I'm starting the backup of all my Jellyfin metadata files now via rsync + SSH ( rsync -av --progress /volume1/@appdata/jellyfin/ /volume1/redacted/JellyFin-Metadata-Backup/ ).

I tried using the file browser app but it doesn't launch for me. I'm going to do my best to put together a guide of my migration process, or attempt lol, and share it with this thread when done. I'm actually moving from one raid to another (4x8TB RAID5) to (3x24TB RAID5) on my DS920+ in the next few days once my drives arrive, so not doing anything just yet. Once drives arrive, I will then setup docker for first time ever on the new raid array, restore all my media files with hyper-backup, then copy my metadata files into my docker container afterwards (I assume, again, brand new to docker). I plan to follow this JellyFin Synology Docker setup guide, it seems the newest and most accurate (https://www.youtube.com/watch?v=X-hpTxdU35g).

The individual who created that guide said "I actually did check out Jellyfin's Synology installation guide and it is actually dated. The way they describe installing Jellyfin is probably what you would do prior to DSM 7.1 (I think) or whenever Synology changed over from the Docker package to Container Manager. If you are using Container Manager, then you probably want to install Jellyfin, and any other Docker containers, using Projects and the .yml configuration file.". I assume he is correct, and his docker-compose.yml code in the description is good?

I plan to setup my synology volumes and folder names exactly the same as my previous RAID array, so I don't think there should be any problems with identification?

[Anon]

Alright, making progress on trying to figure this out, got my new drives and copying my Jellyfin data to new raid array, but I have some questions regarding the .YML docker compose command / which Jellyfin directories need to be included in to ensure all my metadata (library images, watch history, etc), all show back up normally.

Screenshots of my setup / questions: https://imgur.com/a/XFlF3uk

Based on my screenshots, is this docker compose file for jellyfin correct? Do I need to include the data and log folder (or the jellyfin.log and the jellyfin.pid files)? These 4 folders and 2 files all came from @appdata/jellyfin.

---
version: '3.5'
services:
jellyfin:
image: jellyfin/jellyfin:latest
container_name: jellyfin
environment:
- PUID=to fill in
- GUID=to fill in
- TZ=America/Chicago
network_mode: host
volumes:
- /volume1/docker/jellyfin/configconfig:rw
- /volume1/docker/jellyfin/cachecache:rw
- /volume1/docker/jellyfin/datadata:rw
- /volume1/docker/jellyfin/loglog:rw
- /volume1/jellyfinjellyfin:rw
restart: unless-stopped
---

Also, the actual backup of the Jellyfin directory I made using hyperbackup contained it's own @app/@metadata/jellyfin folder, and inside of it, it has folders matching my jellyfin library names, and seemingly containing the actual metadata, the "/config" file I backed up via ssh only has these folders in it:

dlna
ScheduledTasks
users
encoding.xml
logging.default.json
migrations.xml
network.xml
system.xml

I do not see any actual metadata as I know it in the config folder, is this normal?

[TheDreadPirate]

You need to pass in the GPU for transcoding. Your NAS has an Intel CPU, correct?

https://jellyfin.org/docs/general/admini...ial-docker