Migrate jellyfin package to docker container on Synology NAS

[Efficient_Good_5784]

Question #1

So, for each of these folders (inside my primary shared folder), do I need to include the mappings below?

/volume1/jellyfin/Animated ShowsAnimated Shows:rw
/volume1/jellyfin/AnimeAnime:rw
/volume1/jellyfin/Kids MoviesKids Movies:rw
/volume1/jellyfin/Kids ShowsKids Shows:rw
/volume1/jellyfin/MoviesMovies:rw
/volume1/jellyfin/ShowsShows:rw

OR is just the below good enough since Jellyfin is my only true shared folder (the rest are sub-folders inside /volume1/Jellyfin) in Synology?

/volume1/jellyfinjellyfin:rw

This entirely depends up to you. Both is correct.
One benefit of listing each out is that if you ever add a new folder to this location on the Synology nas, it will not show up to Jellyfin (which means Jellyfin will not be able to modify its contents).
You also have finer control over which folders it has read-only or full write access to.

Also as a FYI, you can rename host mounts to be whatever random name you would like.
So this is possible too:

Code:

/volume1/jellyfin:/amazing-media:rw

That host mount would take the Jellyfin directory on the nas and show it in the container as "amazing-media".
The reason I bring this up is because maybe you'll want to reorganize your nas folders, or even switch to another system.
If you end up switching the media from "jellyfin" to another folder named "media", you can still do this:

Code:

/volume1/media:/jellyfin:rw

Jellyfin will require a rescan of all your media if the path changes, but doing the above would prevent that rescan in the first place since the host mount still is seen as the same path as before.

Question #2

These files above did NOT exist in the backup files I copied via rsync + SSH. Instead, when I created a hyperbackup of my Jellyfin shared folder (so I could move files to new RAID array), this @app/@metadata/Jellyfin folder copied over as well, and appears to be 13.5MB in total, with 1128 files and 1127 folders (my media is 10TB in size).

I imagine this is just metadata from the actual Synology Community Jellyfin app, and not important files I need to worry about. Is that right?

Each show/movie folder has a _Syno_BkpMetadata.db file inside.

The files named "_Syno_BkpMetadata.db" are Synology Hyper Backup specific files.
They're in no way related to Jellyfin, so you can safely delete them.
If you miss any of them, I don't think it will cause problems with Jellyfin.

The point of these files in Hyper Backup is that they contain metadata related to your Synology nas so that Hyper Backup can restore your backed-up files when the time comes.
I'm not to familiar with them, so if you desire more info about these if you're curious, you'll need to ask on the Synology forums: https://community.synology.com/enu

Question #3

I copied these two folders data and log into the config folder, but I'm not following why I'd add a duplicate config folder. The config folder I have in my original screenshot is this config folder, with the dlna, scheduledtasks, etc. inside.

I think there's a miscommunication here.
Take a look at the config folder I have for my Synology nas: https://imgur.com/a/1s6NUu5

Look at the sidebar that shows how the config folder is nested inside another config folder.
I would suggest moving around your folders to match what I have. I assume that the Jellyfin image will expect what I have since that's what it created for me by default.

Question #4

Is this line correct based on my above output from my DS920+ Synology? Just want to make sure, I also have card0 listed.

devices:
  - /dev/dri/renderD128dev/dri/renderD128

That should be correct.
You can include card0, but I chose not to include it in the example compose file example since I've seen others previously state that it's not required for Jellyfin to use HWA.

Question #5

Based on above, and under the assumption that /volume1/jellyfinjellyfin:rw is good enough, is below correct? I've changed network_mode to host, as that seems to be what I would want I think.

Code:

services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    container_name: jellyfin
    environment:
      - PUID=1028
      - GUID=100
      - TZ=America/Chicago
    volumes:
      - /volume1/docker/jellyfin/cache:/cache:rw
      - /volume1/docker/jellyfin/config:/config:rw
      - /volume1/jellyfin:/jellyfin:rw
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
    network_mode: host
    restart: unless-stopped

This should be correct as long as you sort the config folder to how it's supposed to be.