· I am trying to install Roon via container station in my QNAP 683. I have followed all steps from this guide:
Roon Labs Help Center
Before you begin - Installing RoonServer on QNAP with Docker This guide explains how to run the official RoonServer Docker image on a QNAP NAS using Container Station. Source: QNAP documentation: Container Station Quick Start Guide. Before you begin Make sure your QNAP NAS has: Container Station installed from...
And although server is up and running it cannot be found by any of my devices. I checked the logs and they had a repeated message about space like the below: (cant copy all of it due to character limit)
roonserver | tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Linq.AsyncEnumerable.dll: Cannot write: No space left on device
roonserver | tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Linq.Expressions.dll: Cannot write: No space left on device
roonserver | Roon Docker image 1.0.6 starting.
roonserver | No existing RoonServer install found under /Roon/app/RoonServer.
I had a similar issue when first trying to install roon docker via Container Station.
Most probably, something is wrong with the share file path you have used in docker generator. Could you please share the first path sharing the folder for :Roon with the container? It probably leads to a folder which is non-existent, on the wrong volume, or prohibited from writing data into it, so Container Station is unable to extract the downloaded .TAR file.
A very common mistake, which not only me, but several users have made in the first place, is including the alias name of the volume in the shared path, for example:
/share/DataVolume/Container/roon:/Roon
This is wrong. The correct path in this case would be:
Hello Arindal and many thanks for the quick reply.
Please be aware that I lack programming skills or terminology knowledge. When I install the container station in my QNAP, I put it in my SSD drive to ensure better speed. When it asks me to create a folder for the data, like the step below,
it only gives me the option to put it in my hard drives where my data is, including my music. I have a folder called multimedia which has my music, and I tell container to install the data there.
The shared folder /Container may live on magnetic HDD volume, no problem. In this case, you should create a separated folder for the roon container, which, unlike the default /Container folder, is on your SSD. It is important to point the first share path in docker generator to this exact folder on SSD, as you don´t want roon to run its database on the HDD volume, and will make it easier to avoid access restrictions for Container Station.
How does the folder hierarchy of your SSD volume look like in File Station? And did you make sure this volume permits read and write for all users?
What idd your YAML install file look like? Have you selected the correct path for the installation? If you need to find the QNAP absolute path, I have found a guide that may help:
means you are installing the container folder where roon and its internal database live in, under the main /Container folder, previously created by Container Station, which might lead to both folder permission/confusion issues, as well as the database living on magnetic spinning discs (which should be avoided).
Could you pls name the path/folder name of your SSD volume, or explain how you have accessed it in the past? A screenshot of File Station volume/top-level folder hierarchy would do.
Hi there. Thanks for the reply. Please see below screenshot of the file manager. Container station is installed in DataVol 1 which is my SSD that I use for apps. The shared folder, as you can see is at the magnetic drives, in the multimedia folder.
So the share path to your Music in Roon, the second path in the docker script, should read:
/share/Multimedia/Music:/Music
Interestingly the /Multimedia folder contains a folder named container-station-data, which is a hint Container Station unsuccessfully tried to install something here, and it seems to have write permission differing from other folders as well.
Are you sure? I don´t see a top-level folder named /Container under DataVol1, maybe it is hidden or you have to scroll down a bit?
Either way, you have to create a valid path where roon app inside a container and its database can reside on the SSD. The easiest way is to create a new top-level folder, named like /RoonInContainer on DatalVol1 and have the container extracted and run therein:
/share/RoonInContainer/roon:/Roon
/share/Multimedia/Music:/Music
/share/RoonInContainer/roon-backups:/Roon
In this case, the location of /Container folder as used by Container Station, if it is on spinning disc or SSD, which users have which access to it, should be rather irrelevant.
It looks like Container station is indeed installed on DataVol1. But as I don´t see the shared folder /Container under this volume, and Container Station tried to write something into /Multimedia on “Music & Movies” volume, so you need to find a location for the roon container which allows read and write and is clearly accessible by a share path.
No, this is still the same paths which led to error messages.
You need to either figure out the correct path of /Container folder, ideally using system-level names for the volume (presumably DataVol1 which is an alias name), or create a new top-level folder for the purpose of running roon in the container in.
Alternatively, there is another excellent way to fix this that will actually benefit your entire NAS setup.
Instead of creating a new folder and changing the YAML code, we can simply move your existing default Container shared folder to your SSD. This is a “best practice” for QNAP, as it ensures that not only Roon, but all your future Docker applications will run at maximum SSD speeds without hitting any strange storage limits.
If you prefer this route, here is how to do it safely:
1. Stop Container Station (Critical Step)
Before moving any system folders, you must stop the app to prevent data corruption.
Open your QNAP App Center.
Find Container Station, click the small arrow next to “Open”, and select Stop.
2. Move the Folder to the SSD
Open your QNAP Control Panel.
Navigate to Privilege > Shared Folders.
Locate the Container folder in the list.
Click the Edit Properties icon (it looks like a piece of paper and a pencil) under the Action column.
In the properties window, change the Disk Volume dropdown to DataVol 1 (your SSD).
Click Apply. The NAS will now physically move the folder to the SSD.
3. Restart and Deploy
Once the move is complete, go back to the App Center and Start Container Station.
Because the Container folder now officially lives on your SSD with plenty of space, you can use your original YAML file exactly as you wrote it:
volumes:
/share/Container/roon:/Roon
/share/Multimedia/Music:/Music
/share/Container/roon-backups:/RoonBackups`
(Note: I updated your music path to /share/Multimedia/Music based on your screenshots).
Deploy the container again, and the installation should extract perfectly this time!
