My goal is to move from the native Synology app over to the docker version. My reason for that is, sometimes the native app crashes, probably about every 2 months and i’m not able to restart it due to “ERROR - HttpServer: Error binding acceptor: Address in use”. I believe this is caused by the zombie plex process holding onto the port, which I can’t terminate because the parent is the root. I have only been able to get around this by restarting the entire NAS, which is also an issue because it hangs in the restart process indefinitely and I need to be physically there to use the power button at that point. These 2 are related because the NAS restarts fine if i do it when there is no zombie process.
To this end I have been trying to follow @ChuckPa directions at DSM 7 + Packaging 2.0 + Docker -- The How-To as utilizing my existing data and having the native app available as a backup is my ideal scenario. Disclaimer - This is my very first foray into docker and have extremely limited linux experience, if possible please be very detailed for my benefit.
My first problem starts at the container creation segment where i’m supposed to map /PlexMediaServer/AppData` → /config/Library/Application Support. I’m using synology container manager and the mapping interface doesn’t seem to like spaces and I can’t enter ‘Application Support’.
Second thing I don’t understand is how to do is using Docker compose or Docker run to enable the hardware transcoding. I can’t find either of those apps in the package center. I must be misunderstanding this.
Third and lastly, once finished i’m wondering how I can prevent the native app from starting automatically in the event of a reboot, as 2 running instances probably won’t be a good result.
Please let me know if I can provide any further information. As always, the community support is greatly appreciated.
From your original screenshot in the guide it looks like you input in the volume settings. The screenshot in your response here looks to me like the variables section. I don’t know if i may be misinterpreting this.
Once i put a space in that right hand box, it turns red and says incorrect value. I tried to enclose with quotation marks hoping that would assist but that didn’t help either.
For testing, if i remove the spaces or replace them with a - the error goes away.
Got a response from Synology’s automated system. This short version of the response -
The use of space character is a known issue with volume mapping in Container Manager. As a workaround, create the container with erroneous mappings to bypass the limitation then export and edit the json file to correct the values, delete the container and import using the corrected file. If anyone would like to see the response in full, let me know, I would be happy to post.
Using this information I was able to get the container running which now looks like this.
This leads me to my second issue where lack of experience has the better of me. How do I add the --device /dev/dri:/dev/dri to enable hardware transcoding?