You’re using LinuxServer.io’s container.
ADD
PUID = 297536
PGID = 297536
IIRC, they don’t use PLEX_UID or PLEX_GID
1 Like
Ok its up and running but not able to play anything, everything shows up as unavailable.
Look at the container name you gave it.
That’s the name of the server 
Might be better to sign out, then go at it . It’s there. but not by that name.
Worst case, you stop it and manually get the logs just as you did for DSM 6
It lets me play the files if I change file path from (/volume1/data/media/Stand Up Comedy) to (/media/Stand Up Comedy) but then moving back to the bare metal I have to change it back to (/volume1/data/media/Stand Up Comedy)
So I added this for the container and it seemed to fix it.
Ah… it couldn’t find your media?
That would do it 
I see you have two listed, You can directly map in both
What you’re doing is bringing the outside “real world” inside this artificial “bubble”.
If it’s possible to map real → internal, do it. PMS will be very happy
/data/media --- just as you did
/media -> /media -- should be there rest if matching this image
Should that be /volume1/media ??
I only mapped both for the screenshot just so it was easier to visualize.
fair enough 
1 Like
Thanks for all the help!
It doesn’t seem to be hardware transcoding anymore.
Ready for the “Fix” ? You’ll love this one.
- Stop the container.
- Go to the volume tab.
- Map
/dev/dri→/dev/dri← this is where the hardware can be found - Save the changes
- Start
Voila!
If it fusses, there is another way. I’ve not done it in DSM 7 so can’t be 100% sure.
i’m sure those who have hardware transcoding running already will jump in and share
That doesn’t seem to work, I remember reading somewhere it couldn’t be done within the Synology docker GUI, has to be done with docker compose or command line.
EDIT: Hardware acceleration wasn’t checked off in plex server settings DOHHH
OK! LOL
You might be right that it needs docker compose or docker run.
My DS1815+ or DS418j can’t do any of that so I’m not 100% current.
On my Intel, I use --device /dev/dri:/devdri in docker run
Ahh I see, I cant see me leaving the Synology ecosystem, might get a Synology router next. Are there current issues with transcoding HEVC my god it likes my CPU lol
No issues with leaving the GUI ecosystem…
Here, on the command line, you can see the image and the GUI created container.
Synology simply adds their GUI on top of regular docker.
IIRC, you can create it here and then administer it in the GUI.
(( Here = either type on the command line OR create a scheduled task to create/update it))
bash-4.4# docker image list
REPOSITORY TAG IMAGE ID CREATED SIZE
plexinc/pms-docker latest 4fb5fcb5efb8 8 days ago 642MB
SynologyDSM 6.1-15101 58ec61b42c25 4 years ago 586MB
bash-4.4# docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
73861f9db24d plexinc/pms-docker:latest "/init" 33 hours ago Up 19 seconds (healthy) PMS-Packaging-2-0
bash-4.4#
I see, well thanks so much again you’ve really gotten my system fine tuned!
You DO realize, at some point, you’ll need do this on your own? 
I mean granted I have done a lot myself
But yes, learning more everyday.
if you start searching around the forums, now that you understand more, see what you can find & learn .
Im diving into HEVC, seeing how to optimize my server for it. Read about the VaapiDriver, seeing if it helps at all.
