[Moderator edit: split out to own topic.]
Good for you.
My installation of Roon on my compatible Synology NAS failed with a download error. I shouldn’t have touched it.
Good start folks…
I guess you will just keep posting this same comment on every thread?
@KMM
Check the document to run Roon Server in docker on your Synology NAS.
Good luck, Frank.
it is my understanding that DSM 7.2 and above will not be affected by the platform change. I moved my server to a capable notebook and wait and see.
For a regular user, setting up this docker thing is a mess. Instructions are plain misleading, copy something is not the same as downloading something just to start with. The document lacks visuals and reminds me of a geek project. Still not able to set it up correctly on a plain Jane DS720 with the latest DSM. The previous system by Christopher Rieke ran great and I had no issues for years. Great job Roon.
I still run Christopher Rieke image on my Synology, no need to use docker if you’re on the latest DSM
Roon offered me a update for the NAS and I foolishly accepted it. I will now try to reinstall Rieke’s image and if I don’t get these wonderful upgrades so be it.
I’m not sure, but I don’t think Roon would push you to a docker install?
I might give the docker setup a try later, but for me I only updated Roon server (within Roon as usual)
@moonshiner It probably didn’t. But the update offered failed to download several times. At the end, I reinstalled the Rieke version from the scratch and miraculously, I am now on 2.65 on my NAS. They scare people with this docker nonsense for recent Synology DSMs. It appears as you said not needed at all, just a reinstall of Rieke’s version and all is good. Thanks for your help
Sorry things aren’t going very smooth. The docker option is new which unfortunately means we’ll probably miss some things, but we plan on continuously trying to improve it.
Unfortunately, for QNAP and older versions of Synology it is a hard requirement which doesn’t help keep things simple or clear. If it works on Synology for you then you are most likely on a new enough version of Synology that you are safe.
If you ever want to try using docker on Synology we have some instructions here: https://help.roonlabs.com/portal/en/kb/articles/installing-roonserver-on-synology-with-docker
Any feedback on the instructions would be very much appreciated. I don’t personally have a Synology. 
@stephen Thanks for responding. Some feedback on the installation guide:
to 4 : it could read ‘use the download option to save the the generated Docker Compose output to your download folder on your Windows PC’
to 8: it could read’ upload the the generated Compose YAMLfile by using the upload option of the project tab’ (there is no configuration field etc.)
General: identifying the correct path (its syntax) is more than most users including me are immediately capable of. I received numerous ‘incorrect path’ errors. Why does the composer suggest to use // instead of the \\ to identify a path in Synology?
If the system fails with an error, it is not enough to delete the project in the project tab. Even if you do, you need to go the docker folder on your Synology and delete the configuration file separately. There is a trick: before you access the the docker folder, go to any other folder, open it and then go back to the docker folder. Only then, you see the existing old configuration folder in the docker folder.
Anyway, it appears that these instructions were written by some Linux whizz kid completely missing out on the capabilities of the target audience. Anyway, I got it to run with Rieke’s version and I am not going back to the Docker option unless there is some automation available to set it up.
I just found this post by Christopher Rieke which explains the future of his software. Looks like at some point we all have to move to the Docker solution. I hope Roon finds a solution that is as easy to install and use as the Rieke version is.
Stephen,
Yesterday I’ve got same problem - my iPhone app asked me to update room core and after update I cannot start Roon on Synology NAS.
I’ve checked instructions for migrating to docker, but there is 2 moment very unclear.
-
adding image “
https://ghcr.io/roonlabs/roonserver:latest“ to docker app in Synology returns error “Invalid Docker Repository Image”. Adding “ghcr.io/roonlabs/roonserver“ returns “registry returned bad result” -
https://help.roonlabs.com/portal/en/kb/articles/installing-roonserver-on-synology-with-docker#Method_1_DSM_72_or_later_Using_Container_Manager_Projects
here in section “Method 2: DSM 7.1 or older (Using the legacy Docker app) / Migrating from a Native Installation“ mentioned “If you are moving an existing Synology Roon installation into Docker, use Roon’s built-in backup and restore:“ but after latest update to 2.65 my old installation do not start.
Would be nice if instructions revised. I have quite old DSM 6.2, but prior to yesterdays upgrade to 2.65 all was working fine
Same issue as above, running DSM 6.2.4-25556 Update 8. I’ve got plenty of docker images running, so haven’t a clue why this won’t work.
Added it via portainer and it was available in my image registry.
This update also broke Christopher Rieke’s package for DSM 6.X.
Same, update broke Christopher Rieke’s package.
Updated DSM to 7.1, still error from Docker for “https://ghcr.io/roonlabs/roonserver:latest“ - “Invalid Docker Repository URL”
Finally got it to work with version 1 for DSM 7.2.
Don’t forget to stop the Rieke app before you begin with the docker installation.
You can find the accurate path to each of the shared target folders on your Synology NAS under properties:
click on properties and copy the path from this:
Takes out the guesswork and it works now. Added new folders in my existing target folders, so that the new version does not damage the Rieke files. Uninstalled Rieke app after setting everything up
KMM, were you able to restore a backup? That’s been my biggest headache. I’ve followed the guide and docker deployment is working, but every time I restore a backup it just loads an empty roon.
The backup / restore process is normally the easy part.
I pointed my qnap docker install to the directory where my other Roon backups were already residing (from my mock laptop) and just restored the latest, was up and running in a few minutes.
Just followed the normal restore procedure from the kb
Maybe my mistake was making a new backup spot for the docker container instead of the original…hmm
If the old one still exists you can just remap it in the yml file
@KMM I really appreciate you taking the time to providing some feedback. I’ve shared the post with the person working on the docs. I know this isn’t all perfect (yet…), but we are working on it. I’ve trying to keep up with all the feedback and to not miss anything
I’m working on trying to set up the Synology NAS software in a VM so that I can at least see and better understand what everyone is experiencing.