Broken OS Permissions

[Spyderturbo007 19]

I'm hoping someone can help me because I am really in a bind.  I have Emby running on unRAID and performed a v6.9 -> v6.11 upgrade on unRAID, which started causing permission issues with Emby and Sonarr.  Those were the two docker containers that were broken during the upgrade of unRAID which apparently changed the way permissions were applied.

There was no real fix and I tried getting help multiple times in the unRAID forums, without much luck.  I ran into someone that told me running this command in unRAID fixed their issues by resetting permissions on the unRAID AppData folder that holds all the containers.

chown -cR nobody:users /mnt/user/appdata
chmod -cR ug+rwX,o-rwx /mnt/user/appdata

Unfortunately, that seems to have broken Emby.  It works and can write to the array, but the permissions must be wrong on the EmbyServer folder.  I'm getting an error when Emby tries to write the configuration backup to the EmbyServer folder.  I am also locked out of the EmbyServer folder from inside of Windows.

I can delete the container, but I would think that would delete the database and I'd lose all my settings?  I have the configuration backup from the last time it successfully ran, but there have been changes to the media folders since that backup.

I think the best bet might be to nuke the container, reinstall Emby and then try and restore everything (settings, watched status, etc) from a backup.  Does that sound like a good plan?  What's the best way to accomplish that because I can't create a new backup?  Unless there is a way to re-map the backup to a new directory?  Or maybe I can fix the permissions somehow?

Thank you so much!  I'm at a loss and I use Emby everyday.

[Luke 42077]

@Q-Droiddo you have any suggestions?

[Q-Droid 989]

I don't use unraid so don't have anything specific to offer.

To at least understand what might be going on.
- Figure out the actual user:group running the Emby server. It might not be nobody:users.
- Figure out the actual location of the AppData/EMBY_DATA (/config in the container).
- Then the commands above might work if the true user:group and locations are used.
- You can run chown with the numeric uid:gid as an alternative to user:group.

Again, this is unraid and though it sounds like their own devs "broke" the update it is usually best to not fight it on the back-end without an understanding of the consequences.

My general recommendations for Linux and Docker might be too late for this case.
- Take control of uid/gid to run applications. In other words stop using default uid/gid from templates and create a dedicated user:group before installing software and containers. Similar to how the Emby host installation works.
- Make sure AppData/EMBY_DATA are on persistent storage (/config in containers) and not in the container image. This preserves the config and data when recreating or upgrading the image.
- Configure the AppData and media storage so that the app runtime uid/gid has the access it needs.
 

Edited April 8, 2023 by Q-Droid

[Neminem 1518]

From what i can tell, emby server has this owner in unraid , daemon.

Not sure if this is usefull in anyway.

This docker is the official image from emby/embyserver - Docker Image | Docker Hub