This guide explains how to run the official Roon Server Docker image on a Synology NAS. The setup process depends on your DSM (DiskStation Manager) version.
Make sure your Synology NAS has:
Container Manager (for DSM 7.2 or later) OR the legacy Docker app (for DSM 7.1 and older) installed from the Package Center.
x86_64 / amd64 processor. ARM is not supported.
4 GB RAM minimum.
Roon Remote devices on the same local network as the NAS.

Note: We strongly recommend storing the Roon database on SSD-backed storage for optimal performance. On Synology, this usually means placing the /Roon folder on an SSD-backed volume (often the system volume) rather than on a spinning disk expansion storage.
Synology Container Manager (introduced in DSM 7.2) supports Docker Compose through "Projects". This is the recommended setup method because the configuration generator can do the heavy lifting for you.
Open the Roon Docker Configuration Generator.
Select Synology as your platform.
Enter your timezone and folder paths. It is strongly recommended that the Roon data path points to SSD-backed storage.
Copy the generated Docker Compose output.
Open Container Manager on your NAS.
Go to the Project tab and click Create.
Give the project a name, for example roonserver.
Paste the generated Compose YAML into the configuration field.
Review the volume paths to ensure they match your NAS structure.
Click Next, then Done to deploy.
If you are running an older version of DSM, you must use the standard "Docker" app and configure the container manually via the graphical interface.
Open the Docker app on your Synology NAS.
Go to the Image tab, click Add, and choose Add From URL.
Enter https://ghcr.io/roonlabs/roonserver:latest (leave the Hub Page blank) and click Add. Wait for the image to download.
Once downloaded, select the image and click Launch.
Network: It is critical to select "Use the same network as Docker Host" (this is Synology's term for Host Networking). Roon will not be able to discover your audio devices without this.
Advanced Settings / Volume: Click Add Folder to map your Synology host folders to the container paths:
Map your Roon folder to /Roon
Map your Music folder to /Music
Map your Backup folder to /RoonBackups
Environment: Add a new variable named TZ and set the value to your timezone (e.g., America/New_York or Europe/London).
Check the box to Enable auto-restart.
Click Apply or Done to start the container.
RoonServer uses three main storage locations:
Purpose | Container path | Notes |
Roon data | /Roon | RoonServer state: database, settings, identity, logs, and application files. Must be writable and persistent. SSD-backed storage is strongly recommended for the best experience. |
| Music library | /Music | Your local music library. This can usually be mounted read-only. |
Roon backups | /RoonBackups | Optional but strongly recommended. Configure backups in Settings > Backups. |
Host networking is absolutely required for Roon discovery. Without it, Roon Remote may not find the server, and the server may not discover audio endpoints on your network. Also, ensure your container is set to restart automatically after a NAS reboot.
Two release branches are available:
production — stable releases. This is the default and does not require extra configuration.
earlyaccess — pre-release builds, updated more frequently.
If you are using Method 1 (Compose), you can set this via the configuration generator. If using Method 2, add an environment variable ROON_INSTALL_BRANCH with the value earlyaccess. Switching channels takes effect on the next container restart.
If you are moving an existing Synology Roon installation into Docker, use Roon's built-in backup and restore:
In your current native Roon installation, disable all watched storage folders (Settings > Storage). This avoids path conflicts after migration.
Create a backup (Settings > Backups > Back Up Now).
Stop the native application.
Copy the backup to a location accessible from your new Docker host mapping (e.g., your /RoonBackups folder).
Start the new Docker container. On first launch, it will prompt you to set up or restore.
Choose Restore and point it to the backup.
Once the restore is complete, edit your music folders' paths with the paths as they appear inside the Docker container (i.e., /Music).
Confirm the container is running in Synology's Container Manager or Docker app.
Open Roon on your phone, tablet, or computer.
Make sure the device is on the same local network as the Synology NAS.
Select the Roon Server running on the Synology NAS.
Set up a new Roon Server or restore from backup.
Go to Settings > Storage and confirm your music folder is visible.
Roon Remote cannot find Roon Server Confirm that "Host networking" (or "Use the same network as Docker Host") is enabled and that the Roon Remote device is on the same local network.
Performance is poor Confirm that the /Roon mapping points to SSD-backed storage. For the best experience, the Roon database should not live on a spinning disk.
Music folder is missing Confirm that the Synology host folder exists and is mapped to /Music inside the container. In Roon, use the container path (/Music), not the Synology host path.
Permission problems Confirm that the Docker/Container Manager service has read/write permissions to access the Synology host folders you mapped for /Roon and /RoonBackups, and read permissions for /Music.