Plex DSM 7 Docker 2.0 Packaging DS920+

[manish_vallabh_mv_gmail_com]

Server Version#: 1.24.2.497
Player Version#:n/a

First wanted to say great work with the 2.0 packaging with DSM 7. I never had any issues migrating from DSM 6, and everything has been working great. I’m on the public builds so I upgraded to 1.24.2.497 and was happy to see the new folder structure.

I tried to setup the docker to access the new folder structure as per Chuck’s post

DSM 7 + Packaging 2.0 + Docker -- The How-To

DSM 7 + Packaging 2.0 + Docker – The How-To This How-To (FAQ) will demonstrate how to setup a pms-docker container which uses the new packaging (/PlexMediaServer/AppData) structure used in PMS 1.24.2.4973 and above (DO NOT USE BETA 1.21.0.3744) and is fully interoperative & non-destructive of the Native app. (you can run either either as you wish.) A. Get the UID/GID values from DSM 7 for use with PLEX_UID & PLEX_GID Create a Scheduled Task - User script a. Run once b. Email you t…

However I’m getting some errors. Was hoping for some direction.

Using the following to setup docker. PUID and GUID are correct and from my system. confirmed by checking /etc/passed

docker run -d --name=plex
-e PUID=297536
-e PGID=297536
-e TZ=America/Toronto
-e VERSION=docker
-e CHANGE_CONFIG_DIR_OWNERSHIP=false
-v “/volume1/PlexMediaServer/AppData:/config/Library/Application Support”
-v /volume1/PlexMediaServer/AppData/tmp:/transcode
–restart always
–net=host
–device=/dev/dri:/dev/dri
plexinc/pms-docker:latest

I’m getting a error in the log in the docker GUI.

PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server

so the server is stopping.

I also assume I will need to map my media to /data

i.e. -v /volume1/Media:/data \ ?

The goal is to use the new folder structure in docker and test the native package vs the docker package and see what performs better.

p.s. I have found that by using the VaapiDriver=“i965” I can view live TV with subtitles which doesn’t work with the iHD driver.

Thanks
M.

[manish_vallabh_mv_gmail_com]

Any thoughts? when I check the permissions within the docker container I can see that it only has rx on the users and groups, and have double and triple checked the GUID and PGUID is set correctly, DSM shows the User ID has RW access to the folders and files?

I guess I could change the PUID/PGID to a different user ID which is a admin but don’t want to break the native app which currently works fine.

Thanks
M.

[manish_vallabh_mv_gmail_com]

It appears the system account needs RW access to the PlexMediaServer share for docker to get RW access to the files. I was able to add the system account to have RW to the share via file station in DSM and now the docker starts with no errors. Just testing now to see if it works well.

M.

[ChuckPa]

Be VERY careful here.

1. User PlexMediaServer is only granted RW by DSM. DSM maintains permissions here. Not Plex.

2. You must grant System Internal User PlexMediaServer permission to read your media (equivalent to DSM 6’s Plex user)

3. If you change UID/GID then you will break comatibility with PMS and those permissions asserted by DSM 7. STRONGLY advise NOT changing UID/GID (PUID/PGID – PLEX_UID/PLEX_GID )

4. Do you have logs please ?

[manish_vallabh_mv_gmail_com]

I did leave it as PlexMediaServer user ID, in the docker run command. I only added the SYSTEM account to have RW access via file station as per the screen print.

Here is the docker error prior to adding the system account to have RW access to the PlexMediaServer folder. rename to .html to see it as it exports from the Synology docker UI as .html.

plex.html.txt (15.5 KB)

I haven’t done much testing but did run into problems with the DVR. so I ended up shutting down docker and moving back to the native app, as I had some recording scheduled and had to reload the guide when back on the native app.

M.

[ChuckPa]

I am still having a disconnect why using the account ‘SYSTEM’ makes any difference because it is not a privileged UID/GID.

I believe you’re chasing a red herring there.

This is from our lab DS716plus.

1. No “System” account needed
2. Use PLEX_UID and PLEX_GID as per pms-docker documentation
3. 100% interchangeable with native.

plex
bash-4.4# pwd
/
bash-4.4# id PlexMediaServer
uid=297536(PlexMediaServer) gid=297536(PlexMediaServer) groups=297536(PlexMediaServer),937(videodriver)
bash-4.4# hostname
Syno-DS716plus
bash-4.4# cat dockerplex 
sudo docker run \
-d \
--name plex \
--network=host \
-e PLEX_CLAIM="claim-qrrDP584AkBPeCQtsiyR" \
-e TZ="EST" \
-e LANG="en_US.UTF-8" \
-e PLEX_UID=297536 \
-e PLEX_GID=297536 \
-h dockerplex \
-v /volume1/PlexMediaServer/AppData:"/config/Library/Application Support" \
-v /volume1/PlexMediaServer/AppData/tmp:/tmp \
-v /volume1/PlexMediaServer/AppData/tmp:/transcode \
-v /volume1:/volume1 \
-v /volume2:/volume2 \
--device=/dev/dri:/dev/dri \
plexinc/pms-docker:plexpass

#docker start plex
#docker update --restart=unless-stopped plex
bash-4.4# 

[manish_vallabh_mv_gmail_com]

Thanks Chuck, I did not include the claim token, will try and include the claim token, also will map
-v /volume1:/volume1 \ which I did not have either. Maybe that’s the difference? I will remove system and give it another go, will use your docker run as a template… thanks again.

will report back.

Thanks,
M.

[ChuckPa]

If you already have the server claimed, you don’t need the PLEX_CLAIM.
The token is only used on initial run of pms-docker to autoclaim it.

( this is the same mechanism I use in the package installer )

Those 5 volume lines should be all you need unless you have more than 2 volumes.
(adjust volume1 / volume2 / volumeX accordingly)

[manish_vallabh_mv_gmail_com]

I removed the system account and used the following command.

docker run -d --name=plex \
-e PUID=297536 \
-e PGID=297536 \
-e TZ=America/Toronto \
-e LANG="en_US.UTF-8" \
-h ds920 \
-e VERSION=docker \
-e CHANGE_CONFIG_DIR_OWNERSHIP=false \
-v "/volume1/PlexMediaServer/AppData:/config/Library/Application Support" \
-v /volume1/PlexMediaServer/AppData/tmp:/transcode \
-v /volume1:/volume1 \
--restart always \
--net=host \
--device=/dev/dri:/dev/dri \
plexinc/pms-docker:latest

I’m running the command via the task scheduler via the user root

. just easier than enabling SSH each time and remembering to disable it etc. when testing.

M.

MODERATOR EDIT: Code formatting

[ChuckPa]

Where is this coming from ?

Are you starting manually or letting the container start ?

[manish_vallabh_mv_gmail_com]

I did it one more time from the command line.

I receive the errors in the GUI on DSM.

M.

[ChuckPa]

create a task - user-script, run as root.
email the results to yourself.

ls -la /volume1/PlexMediaServer
ls -la /volume1/PlexMediaServer/AppData

[manish_vallabh_mv_gmail_com]

Here ya go.

Task Scheduler has completed a scheduled task.

Task: Task 20
Start time: Mon, 13 Sep 2021 11:33:56 GMT
Stop time: Mon, 13 Sep 2021 11:33:56 GMT
Current status: 0 (Normal)
Standard output/error:
total 0
d---------+ 1 root            root             626 Sep  9 13:29 .
drwxr-xr-x  1 root            root            1190 Sep  1 00:02 ..
drwxrwxrwx+ 1 root            root               8 Sep  9 13:02 @eaDir
drwx------+ 1 PlexMediaServer PlexMediaServer  640 Sep 13 10:56 AppData
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29 Bitte
legen Sie hier keine Mediendateien ab.
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29 Please
do not place any media files here.
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29 Por
favor, no coloque ningún archivo multimedia aquí.
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29
Veuillez ne placer aucun fichier multimédia ici.
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29
ここにメディアファイルを置かないでください。
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29 请不要在此处放置任何媒体文件。
total 0
drwx------+ 1 PlexMediaServer PlexMediaServer  640 Sep 13 10:56 .
d---------+ 1 root            root             626 Sep  9 13:29 ..
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29 Bitte
legen Sie hier keine Mediendateien ab.
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29 Please
do not place any media files here.
drwx------+ 1 PlexMediaServer PlexMediaServer  194 Sep 13 09:53 Plex
Media Server
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29 Por
favor, no coloque ningún archivo multimedia aquí.
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29
Veuillez ne placer aucun fichier multimédia ici.
drwx------+ 1 PlexMediaServer PlexMediaServer 1182 Sep 13 10:56 tmp
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29
ここにメディアファイルを置かないでください。
-rwx------+ 1 PlexMediaServer PlexMediaServer    0 Sep  9 13:29 请不要在此处放置任何媒体文件。

Easier to see here.

Moderator EDIT: </> CODE formatting applied

[ChuckPa]

Thank you.

The permissions for you PlexMediaServer shared folder are broken.

drwxrwxrwx+  1 root                root                      626 Aug 18 10:33  PlexMediaServer

I’ve checked multiple systems here and all are this way.

Let’s attempt remedy. This is not going to be elegant

1. Stop Docker and PMS native package
2. User-script -

chmod 755 /volume1/PlexMediaServer
chown -R PlexMediaServer:PlexMediaServer /volume1/PlexMediaServer

3. After running–
4. Restart Plex Package (DSM will repair permissions as needed during package start)
5. Stop
6. Docker GUI to start package

[manish_vallabh_mv_gmail_com]

Hmm,

Not sure why it’s still giving me the same error. Your Logic and commands make perfect sense, however I’m still getting the same error after assigning the permissions.

Native app seems to be fine, however docker still gives a error. I did fix a problem I had with the quotes around

-v “/volume1/PlexMediaServer/AppData:/config/Library/Application Support” . <<=== Original I posted

-v /volume1/PlexMediaServer/AppData:"/config/Library/Application Support" \ <<=== quotes moved to the correct place after the : after looking at your example. but I recreated the container and same error.

M.

[ChuckPa]

My Docker skills are basic (as you can see above).

PMS in Docker on Synology should be a basic operation.

I don’t know why it’s not working for you when it works for others.

Maybe someone from the community will have an answer. I’m sorry I don’t.

[manish_vallabh_mv_gmail_com]

Thanks for trying appreciate the help. I will use the native package but since it’s missing HDR tone mapping may just install a separate package fully dockerized to test out that version. I also would love it if DVR transcoding while recording used QSV, instead of having to use a post processing script but I don’t think that’s on the roadmap either.

M.

[ChuckPa]

At some point, we’ll figure out what’s wrong with your host / installation.

I know the container definition works.