Unable to find official Roon Docker image for Synology NAS (ref#W0G780)

[Grant_Butcher]

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Installed Docker on Synology NAS. URL for official Roon Image not working (not recognised) Found image gs1903//roonserver:latest. As this does not appear to be the offical release (although it is working), please advise if I would expect any issues. Alternatively, where can I download the image file required for me to upload in Docker

Tell us about your home network

· Synology NAS 1815+, DSM7.1

[Suedkiez (Just a fellow user like you)]

Did you see this?

RoonServer Docker image is live!

For a long time, Roon users have been running RoonServer in self-managed environments beyond the traditional desktop path - on Linux servers, home labs, NAS systems, and custom-built machines. Those setups are more common than ever, and we are now making that path official. The official RoonServer Docker image is now available, and Docker is now our recommended and supported deployment path for self-managed server environments. docker pull ghcr.io/roonlabs/roonserver:latest Getting started If…

[Grant_Butcher]

Thanks for that

I did see that. Tried to create the .yml file, but Synology did not recognise it as a valid file format when I download it after making some path changes on the volume

Will re-read the documentation and try again

[vadim]

Hello @Grant_Butcher

Thank you for reaching Roon support.

We have prepared the guide for the Synology with Docker.

Installing RoonServer on Synology with Docker

Please let us know if you have any problems following it, and on which step you are stuck.

[Grant_Butcher]

Thanks Vadim

The problem I have, is that when I use the url mentioned in the documentation ( Package roonserver · GitHub ) and try to add under image. I get the following error

Invalid Docker Repository Url: Package roonserver · GitHub

I did try this last weekend and just tried ii again now and still the same error. I am running on DSM 7.1 (DS1815+)

I did use gz1903/roonserver:latest - this allows me to utilise TIdal via Roon, but I cannot added in the path for my local music on my NAS. I have multiple formats for the path, but keep on getting errors. I have already pointed to /volume1/music in the container - but am still not seeing my local files
Hence I wanted to see if I could move the official Roon Image, but this is not working
Also, I tried to create the image using the Configurator and saving the .yml file - but this also did not work - Unrecognised file format

Before the update from last week, my Roon was working perfectly.

Not sure where to go from here

Thanks
Grant

[benjamin]

Thanks for the additional information @Grant_Butcher!

The legacy Docker app on DSM 7.1 has issues pulling images directly from ghcr.io (GitHub Container Registry) via the Images tab “Add from URL” method. When you paste Package roonserver · GitHub there, it will always fail. This is a Synology limitation on older DSM versions, not a problem with the Roon image itself.

The right method is to go to the Projects tab in Container Manager (not the Images tab) and create a project using the compose YAML generated by Roon’s configurator. When you do it this way, Container Manager hands the full compose file to Docker, which does the pull internally, and this works fine even on DSM 7.1, with no custom registry setup, SSH, or third-party tools needed.

Here’s how to do it:

1. Go to the [url=https://help.roonlabs.com/portal/en/kb/articles/installing-roonserver-on-synology-with-docker]Roon configurator[/url] and generate your docker-compose.yml
2. In Container Manager, go to the Project tab (not Images)
3. Create a new project and paste in the YAML content
4. The YAML will start with something like:

yaml

 services:
 roonx:
 image: ghcr.io/roonlabs/roonserver:latest

5. That's also where you'll set your volume mapping for local music (more on that below)

The volume mapping must be done in the compose YAML, not added after the fact. In your YAML, under the service, you need something like:

yaml

 volumes:
 - /volume1/music:/music:ro

The left side (/volume1/music) is the path on your NAS; the right side (/music) is what Roon sees inside the container. Then in Roon’s settings, add /music as your watched folder — not /volume1/music.

Let me know if this helps!

[Grant_Butcher]

Unfortunately this has not worked.

When trying to compose a file, I can compose a .yml file under Docker Configuration Generator, but there is no Project Tab - under the option of Container in Docker to paste the data into, I can only Create an Image, and then only add from url or File

Remember this is Docker under DSM7.1 and not Container Manager under DSM7.2

When adding from file, I get Invalid File format when trying to upload the .yml file

[vadim]

Hello @Grant_Butcher,

Thank you for the clarification.

To completely bypass the limitations of the older DSM 7.1 interface, we can use a quick SSH connection to talk directly to your NAS’s core Docker engine.

First, we need to open the door to the NAS:

Step 1: Enable SSH on your Synology

1. Open your Synology Control Panel and go to Terminal & SNMP.
2. Check the box to Enable SSH service (leaving it on the default port 22 is fine) and click Apply.

Now, you have two ways to launch the container via SSH. Option 1 is the fastest, while Option 2 (Docker Compose) is best if you want your settings saved permanently.

Option 1: The Quick docker run Command

This method uses a single text command to launch the server immediately.

1. Go to our Roon Docker Configurator. Select Synology, choose your timezone, ensure your music path is mapped exactly to /volume1/music, and copy the text from the docker run tab at the bottom.
   

   

2. Open Command Prompt (Windows) or Terminal (Mac).

3. Type ssh your_synology_username@your_nas_ip and press Enter. (Replace with your actual admin username and NAS IP).

4. Type your password when prompted and press Enter. (The cursor will not move while typing).

5. Type sudo -i, press Enter, and type your password again for admin rights.

6. Paste the docker run command you copied and press Enter. The container will download and start!

Option 2: The docker-compose Method (Via SSH)

If you prefer to use the .yml file so your configuration is permanently saved, we can deploy it through SSH instead of the broken Synology GUI.

1. Open File Station on your Synology. Inside your main Docker folder, create a new sub-folder named RoonServer.
2. Inside that folder, create a plain text file named exactly docker-compose.yml.
3. Go to the Configurator, set your paths, click the Docker Compose tab, and paste that exact text into your new docker-compose.yml file and save it.
   
   
4. Open your SSH terminal, log in, and get admin rights (Follow steps 2-5 from Option 1 above).
5. Navigate to the folder you just created by typing: cd /volume1/docker/RoonServer (adjust the path if you named your shared folder differently) and press Enter.
6. Type docker-compose up -d and press Enter. Docker will read the file and launch the server.

Once it finishes with either method, type exit to close the terminal. You will now see the official Roon container running normally inside your Synology Docker app!

Give this a try and let us know which method gets your local music library back online!