Unable to scan media upon migrating to docker container

[SirCode]

I recently migrated my native jellyfin media server instance to a Docker container. Im currently running on PopOS Cosmic (24.04 LTS) and using the latest version of docker I can install right now (28.0.4)

I tried scanning some media / editing the images and info on current media, and nothing ever shows up in search results. Its always blank.

Initially I thought it was the container lacking access to the internet, but Ive since confirmed (by exec'ing into it, and curl'ing google) that it does have internet... So jellyfin is the root of the problem here.

I assume its probably some kind of configuration or config error since I migrated, but I have no idea what could cause it.

I would really appreciate some assistance here

Also it may be related, or a secondary issue, but when I try to edit the settings for a library, it says its in an invalid state and cannot be edited:
   

Heres my docker compose:

Code:

services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: Jellytart
    user: 1000:1000
    ports:
      - 8096:8096
    volumes:
      - type: bind
        source: /media/gscomp/Jellyfin/Data/config
        target: /config
      - type: bind
        source: /media/gscomp/Jellyfin/Data/cache
        target: /cache
      - type: bind
        source: /media/gscomp/Jellyfin/Data/etc
        target: /etc
      - type: bind
        source: /media/gscomp/Jellyfin/Data/logs
        target: /logs
      - type: bind
        source: /media/gscomp/Jellyfin/Media/
        target: /media/gscomp/Jellyfin/Media/
    restart: always

What I see any time I search for images / identify / etc:
   

[SirCode]

And yes... I knew there might be problems from migrating... I tried making a fresh jellyfin install, but its whining about user creation... Im getting errors on the goddamn setup page...

https://pastebin.com/bWFHCUqd

[TheDreadPirate]

You cannot relocate data in this manner when migrating. Jellyfin uses absolute paths when referencing metadata, images, trickplays, etc. You have to leave the bare metal Jellyfin data where it is and then modify the docker container's environment variables, which is documented at the link below.

https://jellyfin.org/docs/general/admini...mpose-yaml

In addition to changing ownership of the files to match the user of the container.

If you wanted to migrate your existing data to a centrally located folder, which is one of the benefits of Docker, you would need to know how to use some SQLite tools to find and replace path strings to the appropriate native docker references.