I’ve generated the Docker Compose File, but not sure I’ve entered the right options under ‘Volumes’? Do these need to match up with specific file paths on the NAS? Or am I creating a completely new Roon server? Any help would be appreciated, everything was working fine before this!
I seem to have now got the server working, but now none of the DAC’s plugged into the QNAP NAS are showing up as audio devices that can be enabled? Previously, they would show up under Audio settings and I could configure them from there. I can see other devices listed (System output, Mac Studio Speakers, BenQ Monitor), but not the actual DAC’s which are the ones I want to use. What should I do to fix this?
IIRC, the Docker container needs to be privileged to have access to (all) host devices or you need to list desired devices explicitly (--device). Might be something Stephen Shaw should look into as it is about “making Roon features available to users using official Docker image and instructions”, I think.
Update: I just noticed that the option is already in the configurator – so the next question is: Did you use it?
Would you mind explaining how you were able to add the correct path to your music? I ran into the exact same problem now that I had to move the server to the docker.
@Koen_Van_Den_Hende I just generated the Docker using the configurator and it automatically found the right location for my existing music folder. It seems to create a new Roon app anf backup folder in another location as well. I lost all my existing metadata/favourites/playlists. Sorry it’s not clearer, I’m not an expert in how these file structures work.
Thank you. I removed the application and started again with the script but this time I edited the path to my music library instead of doing it in container station. That did the trick.
Sadly I also need to start from scratch as my backup is nowhere to be found.
You could point to the old data/database directory. Or, you could also point back to the old directory and run a backup. If you already have a backup, you should be able to restore it.
I’d like to clarify a very important step: simply specifying the backup path in your Docker configuration (mapping the volume) only makes the folder accessible to the container. Roon will not automatically detect or import your old database just because the folder is there. You must manually trigger the Restore function within the Roon interface.
How to perform the restore:
The Restore Link:
From the Welcome Screen: If you are on the initial login screen, look for the small “Restore from backup” link at the very bottom.
From Settings: If you’ve already logged in, go to Settings → Backups and initiate the restore from there.
Navigating the path: When Roon asks where the backup is, navigate to the folder you mapped as /backups inside your container and select your most recent backup set.
Understanding Docker Folder Mapping (Volumes): To help you better understand how this works, think of Docker volumes as a bridge between your QNAP NAS and the isolated Roon container. When you look at a volume mapping (for example, /share/CACHEDEV1_DATA/Music:/Music), it always has two parts separated by a colon (:):
The Left Side (Host Path): This is the actual, physical location of your files on your QNAP NAS (e.g., /share/CACHEDEV1_DATA/Music). You can find this absolute path in QNAP File Station by right-clicking your folder and selecting Properties.
The Right Side (Container Path): This is the “virtual” folder name that the Roon container sees inside its isolated environment (e.g., /Music). Keep this simple and recognizable.
Adding Multiple Music Folders: If your music is stored in several different locations across your NAS, you can add as many as you want! Here is how to do it correctly:
Map your absolute QNAP path on the left to a new virtual path on the right for each location (e.g., /share/CACHEDEV2_DATA/Jazz : /Jazz).
Inside Roon: Once the container is running, open the Roon app and go to Settings → Storage. Click “Add Folder”, and browse for the “right-side” virtual folder names you created (e.g., /Music, /Jazz).
Remember, Roon is completely blind to the outside mapped paths, so you will only see and select those simple container paths. Once you map the left to the right and add them in Roon’s settings, it will happily read your files as if they were on a local drive.
Standing by if you need further help with the folder mapping!
Thank you for the update. It is described in the main topic here:
We are constantly workin on improving of our documentation and your feedback is valuable, I will add something explaining on how it works and how to properly use it.