This guide explains how to run the official Roon Server Docker image on an ASUSTOR NAS using Portainer.

Useful Links:

• GitHub repository: https://github.com/RoonLabs/roon-docker

• Configuration generator: https://roonlabs.github.io/roon-docker/

Before you begin

Make sure your ASUSTOR NAS has:

• ADM 4 or later.

• Portainer installed from App Central.

• 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. When possible, place your /Roon folder on an SSD volume rather than on spinning disks.

Recommended method: Portainer Stack

ASUSTOR commonly uses Portainer to manage Docker containers. In Portainer, a Docker Compose configuration is deployed as a "Stack". This is the recommended setup method because the configuration generator creates the exact Compose file you need.

1. Install Portainer from App Central if it is not already installed.

2. Open Portainer and connect to the local Docker environment.

3. Open the Roon Docker Configuration Generator.

4. Select ASUSTOR as your platform.

5. Enter your timezone and folder paths. Make sure the Roon data path points to SSD-backed storage when possible.

6. Copy the generated Docker Compose output.

7. In Portainer, go to Stacks.

8. Click Add Stack.

9. Give the stack a name, for example roonserver.

10. Paste the Compose file from the generator into the web editor.

11. Review and adjust the volume paths to match your NAS directory structure perfectly.

12. Click Deploy the stack.

Storage mappings

Required settings

• Network Type: Make sure the generated configuration uses host networking (network_mode: host). Host networking is required for Roon discovery. Without it, Roon Remote may not find Roon Server, and Roon Server may not discover audio devices on your network.

• Restart Policy: Make sure the stack or container is configured to restart automatically after a NAS reboot (e.g., restart: unless-stopped).

Release Branches

Two release branches are available:

• production — stable releases. This is the default.

• earlyaccess — pre-release builds, updated more frequently.

You can set this via the configuration generator before copying your YAML. Switching channels takes effect on the next container restart.

Migrating from a Native Installation

If you are moving an existing Roon installation into Docker, use Roon's built-in backup and restore:

1. In your current native Roon installation, disable all watched storage folders (Settings > Storage). This avoids path conflicts after migration.

2. Create a backup (Settings > Backups > Back Up Now).
   

3. Stop the native application. 

4. Copy the backup to a location accessible from your new ASUSTOR host mapping (e.g., your /RoonBackups folder).

5. Start the new Docker container. On first launch, it will prompt you to set up or restore.

6. Choose Restore and point it to the backup.

7. Once the restore is complete, edit your music folders' paths with the paths as they appear inside the Docker container (i.e., /Music).

After installation

After the stack is deployed:

1. Confirm the container is running in Portainer.

2. Open Roon on your phone, tablet, or computer.

3. Make sure the device is on the same local network as the ASUSTOR NAS.

4. Select the Roon Server running on the ASUSTOR NAS.

5. Set up a new Roon Server or restore from backup.

6. Go to Settings > Storage and confirm your music folder is visible.

Common issues

Roon Remote cannot find Roon Server Confirm that host networking is enabled and that your Roon Remote device is on the same local network as the NAS.

Performance is poor Confirm that the /Roon mapping points to SSD-backed storage when possible. The Roon database should not live on a spinning disk if you want the best experience.

Music folder is missing Confirm that the ASUSTOR host folder exists and is mapped to /Music inside the container. In Roon, use the container path (/Music), not the ASUSTOR host path.

Permission problems Confirm that Portainer and the Docker daemon have permission to access the host folders used for /Roon, /Music, and /RoonBackups.