Jump to content

Migratinging from Emby Server as a package to a docker install/deployment


Go to solution Solved by jerkrl,

Recommended Posts

jerkrl
Posted

Hi,

On my Synology DS720+, I have Emby Server installed as a package.
I'm trying to migrate my Emby Server to a docker container installment (deployment), as I intend to move my Emby Server from my Synology to a linux server that is more powerfull.
I would like to do so, while keeping all the info/data of my current (package) installment and have them used after I have deployed the docker container. Effectively, Emby Server as it was before without any additional setup required, as it is the exact same server.

I tried, but... it gives me the first-time-setup page.

What I have done till now:

  1. Stop the package
  2. Copy everything in @appdata/EmbyServer to the new location where my docker containers are residing

    cp -ar /volume2/@appdata/EmbyServer/* /volume2/docker/emby_server/
     
  3. Set the ownership:

chown -R 1026:100 /volume2/docker/emby_server/
chmod -R 775 /volume2/docker/emby_server/

  1. Confirm all is copied
  2. Start the Emby Server docker container
  3. Go to http://192.x.x.x:8096
  4. "Welcome to Emby
    This wizard will help guide you through the setup process of setting up Emby Server."

So, my approach is not fully working.
What am I doing wrong?

jerkrl
Posted

... I have gotten a bit further by using Save Back Up & Restore

Emby now looks likes it is the same, same CSS, media info etc.
But I cannot changes images nor play any file/movie ("No compatible streams are currently available. Please try again later or contact your system administrator for details.")

 

Posted
2 hours ago, jerkrl said:

... I have gotten a bit further by using Save Back Up & Restore

Emby now looks likes it is the same, same CSS, media info etc.
But I cannot changes images nor play any file/movie ("No compatible streams are currently available. Please try again later or contact your system administrator for details.")

 

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

  • 2 weeks later...
  • Solution
jerkrl
Posted

I've managed to fix this issue, with a lot of help of Claude.
And I've asked it to summarize what happened:

Situation: Emby Server 4.9.3.0 running in a privileged Debian 12 LXC on Proxmox, with media stored on a Synology NAS mounted via NFS. After migrating Emby data from the Synology (instaled as package) to the LXC, Emby could not read the media files. The UI returned "Access to the path is denied" when adding a library folder, and playback gave "No compatible streams are currently available."

Environment:

  • Proxmox host mount: 192.168.xx:/volume1/data/mnt/yyyy-media
  • LXC bind-mount: mp0: /mnt/yyyy-media,mp=/media
  • NFS export on Synology: no_root_squash, files owned by UID xxxx, group users (GID xxx)
  • Directory permissions: rwxrwxrwx (777)
  • Emby user: uid=999(emby) gid=996(emby) groups=996(emby),44(video),104(render)

Symptom: Root could read the files without issues. The emby user could not, despite 777 permissions on all directories. Both the Emby UI folder browser and playback failed with permission errors.

Root cause: NFS access control operates at the UID/GID level, not just on permission bits. The emby user (UID 999) did not match the file owner (UID xxxx) and was not a member of the users group (GID xxx) that owned the files at the group level. Even though the permission bits showed world-readable/writable, the NFS client-side access check denied the emby user access.

Fix:

bash

usermod -aG users emby
systemctl restart emby-server
usermod -aG users emby
systemctl restart emby-server

Adding the emby user to the users group (GID xxx) — matching the group owner of the files on the NFS share — resolved the issue. After restarting Emby, both library browsing and playback worked immediately.

Takeaway: when running Emby with NFS-mounted media, don't just check directory permissions. Verify that the emby user is a member of the group that owns the files on the NFS server. Permission bits alone don't tell the full story with NFS.

  • Like 1
  • Thanks 1
Posted

Hi, thanks for following up !

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...