-
-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] PUID & PGID have not worked for some time. Changing to original PLEX labels works. #390
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Logs is important. post logs from a restart of the container, with PUID and PGID set. |
I thongs the logs would be more detailed this, not seeing where to increase verbosity or container logs which begin with the ascii logo. using
|
Those logs are not from our image. The compose yaml you posted above includes duplicate image settings, one pointing to ours, one pointing to Plex's. Those are the settings you need to fix. |
Aha! Sorry I didn't see this late last night, I have removed the duplicate image, and all is working well again....
|
Is there an existing issue for this?
Current Behavior
Setting the PUID and the GUID has not worked for some time, I think I actially moved away from Linuxserver.io because I couldn't delete files from the Plex interface even though:
id plex >
uid=1031(plex) gid=65536(sc-automedia)
PUID=1031
PGID= 65536
I have my media folders owned by plex:sc-automedia with permissions 775.
The values for the labels don't really work with the code, because the code is expecting to see PLEX_UID and PLEX_GID when deleting files..
Expected Behavior
- PUID=1031 # does not work as suggested on linuxserver
- PGID=65536 # does not work as suggested on linuxserver
Steps To Reproduce
If we use the original Plex labels in docker commands or compose files, everything runs perfectly.
- PLEX_UID=1031 #original PMS will work fine with folder permissions and
- PLEX_GID=65536 # use these working labels instead
Environment
CPU architecture
x86-64
Docker creation
Container logs
I didn't dig through the logs because changing the labels obviously works with all the permissions I have had set for years.
The text was updated successfully, but these errors were encountered: