· None of the above quite fits
· None of these quite match
· Unable to update Roon on QNAP TVS471 using How To guide
· Wired Network, Roon Server on QNAP TVS471uk using i7 processor and 16gb memory. Router is YouFibre, NAS connects via two switches to Devialet Expert Pro 220.
Hello @Rob_Gardner,
Thank you for the detailed screenshots! They make it very easy to see exactly where the configuration is hitting a snag.
Looking at your Container Station screenshot, the issue is that you have pasted a docker run command into the YAML editor. While that command contains all the right information, the “Create Application” feature in QNAP requires a specific format called YAML (a docker-compose file) rather than a single-line terminal command.
How to fix this:
Go back to the RoonServer Docker Configuration Generator page.
In the top-right toggle of the code window, make sure docker-compose.yml is selected
Copy the entire block of code that starts with services:.
Return to Container Station, clear out the current text in the YAML code box, and paste the code starting with services: there.
Once you paste the proper YAML format, the “Validate” button should check out successfully, and the “Create” button will become active. This will spin up the official Roon container and get your NAS back into action!
Please let us know if you run into any validation errors after pasting the services: block.
In addition to what @vadim was pointing out correctly, from practical experience, creating/storing a .yml file in docker generator and uploading that one in Container Station via ´Create application > Upload´ has proven to be the most reliable path.
One remark: Your share paths as inserted in docker script, contain device names (“NASF68149”) plus volume alias names / logical names, like “Data_Vol1” or “Music_Vol1”. Both might lead to the share path ending up as non-functional (resulting in error messages like ´No space left on device´ or empty folder as seen from container). If your top-level folders like /Container are correctly shared/mounted and not redundant, you can leave out the volume name from the path, like:
/share/Container/Roon:/Roon
/share/Music:/Music
in your case.
If that is not working, you have to figure out the individual volume names as used on system level, as the top location following /share, that could be for example CACHEDEV1_DATA instead of Data_Vol1.
Many thanks to the two of you. I will have another go and let you know how I get on!
Hello @Rob_Gardner
Please keep us posted with any progress.
I did manage to get the suggested code uploaded onto Container but Roon refuses to connect to my ipad and the app on my qnap shows Roon as “stopped”.
When I look at the Roon folders in container they are all empty.
Should there be files in the folders?
Hello @Rob_Gardner,
You are absolutely right to ask—there should definitely be files in those folders! When the Roon container starts, it immediately writes its database and configuration files into those mapped directories.
If the folders are completely empty and the container instantly jumps to a “stopped” state, it means Docker is physically unable to write data to your NAS drive. On a QNAP, this almost always comes down to one of two things: either the folder was created on a partition with no free space, or Docker lacks the permissions to write to it.
Here is what we need to check directly in your QNAP settings:
Sometimes QNAP defaults to creating new Shared Folders on a small, hidden system partition that is already full, rather than on your main storage drives.
Container folder (or whichever folder you mapped Roon to) and check which Volume it is located on.Container folder.If you verify that the folder is on a drive with plenty of free space and has full Read/Write permissions, but the container still stops instantly, there is likely a small typo in the folder paths you entered into Container Station.
We will check the paths for you to ensure everything aligns perfectly with your QNAP’s file system. Let us know what you find in those folder settings!