No they have Docker available in their app store thing. It’s version 20.10.3
Who has it?
I have a DS418j (ARMv8), running build 7.0.41882.
I have no Docker available to install.
That’s strange. I’m looking at it right now in Package Center. I had read months ago that Synology indicated it would be available and updated to the latest version of Docker once DSM was out of beta
https://www.synology.com/en-us/dsm/packages/Docker
Looks like the DS418j is not in the compatibility list
Check out my link above. I don’t see your model in the compatibility list. They must have cut out some models with the move to DSM 7
Yes mine is a DS918+
Well, if that doesn’t just screw the pooch.
Oh, they cut a LOT of things. Cut so much that this is going to cost them bigtime in he long run.
So— back to your question –
Existing DSM 7 plex installation
- Move the contents of
/var/packages/PlexMediaServer/hometo the appropriate space in your/configlocation. - Reconstruct the
Library/Application Supporttop level directories (think Docker Plex wants that)
Existing DSM 6 plex installation
- Move the contents of
/volume*/Plex/Libraryto wherever (or just leave it if you wish
It’s pretty stupid to cut an ARMv8 CPU when it’s 4-5x faster than most of the crap they’re keeping.
do you need to SSH in to the NAS to access the /var location?
yes, and you must be root.
(this is where they had cut me off at the knees. No ‘root’ during package install. DSM does it for me. I only see user “PlexMediaServer” (the package name))
From a host/system security & stability standpoint, I can see that being a useful viewpoint. Obviously, if you’e going to ban use of the administrative account, you will have to provide mechanisms to allow administrative activities through a request mechanism of some sort. This would be a major change, and without buy-in from the 3rd party package builders, I’d expect a significant reduction of available packages.
100% correct.
Where we unfortunately stand now is:
- We just got this full redesign / rewrite completed, which supports 8 spoken languages, done
- Synology has informed us of more breaking changes to come.
- They don’t know what those breaking changes will look like when done but they know our packaging will again be broken.
If these upcoming changes were about security, I could understand but they aren’t.
They’re removing those very same WIZARD_UIFILES we just crafted in all those languages at minimum.
They will try to have an alternative solution for us to use but have no idea what that will look like at this point.
This was the “Money → Hole” problem which we couldn’t solve and our management said “Hold”.
So “Hold” we shall until we see some developer’s documentation and have have something in hand to ‘kick the tires’.
All DSM 6 will continue uninterrupted.
All DSM 7.0 - 41222 & 41882 will continue uninterrupted.
Nothing after that unless approved by management.
Kudos to the Plex team for even trying to make things work at all in this situation. It’s insane that Synology has an “RC” release yet the packaging is not even nailed down yet…
Unfortunately, I jumped the gun way early and had to switch to a Docker release of Plex (all is well by the way). This whole situation is the final nail in the coffin for me with regards to Synology products (still no 2.5Gbe come on…).
Just wanted to say “thank you” Plex!
Cheers,
@ChuckPa Thank you for all your effort! Be sure that it is very much appreciated. You are giving us Synology-based users an awesome support.
1 Like
On my Synology I added a startup script to put /volume1/@apphome/PlexMediaServer/Plex Media Server/Logs (default logs location) in a ramdisk to limit activity on the internal disks.
I really can’t recommend this unofficial “trick” but I’ve been doing this for a long time (way before DSM 7) and haven’t noticed any drawback, except that the logs get cleared when I restart my NAS
- if you want to put logs on a ram disk or something —
- You could always use the supported method I provide in the package installer
— Just sayin’ 
I don’t know why logs are going to a ramdisk – zero gain.
The database is just as active when PMS is running.
Yes, maybe I’ll try again when DSM7 support is officially restored At the moment I have version 1.23.2.4600 on DSM 7.0-41882 (upgraded from beta) and it’s working like a charm, so I’m not touching anything else.
Thanks for all your efforts with these DSM packages, this must be a very frustrating time for you…
1 Like
I am exactly in the same situation (1.23.2.4600 on DSM 7.0-41882). Everything works perfectly. If I have well undestood, in order to get a futur Plex upgrade, the Synology / Plex problem has to be settled ?
Repeating:
- I have changed the packaging to be Build 41222 and Build 41882 compatible.
- The change is in Engineering & QA review – fingers crossed ; maybe next release
- DSM 7 is about to release ANOTHER version.
- Plex will work – PROVIDED Synology hasn’t made more changes to the SPK format.
Most Importantly.
- DSM 6 will continue without interruption
- DSM 7 - Build 41222 will continue without interruption
- DSM 7 - Build 41882 willl continue without interruption
- Future builds of DSM 7 may work – If so then great.
- Plex’s engineering time for chasing Synology is frozen until Synology is again stable.
4 Likes
Hi
Where can i find the build 41882 compatible packing? The one i download from plex pass gives invalid file structure! (1.23.3.4692-c86c6f454) DS1819+
Regards
Jack
Scroll back in this thread …
And you’ll find my links.
But here’s the link again, to that same thread
