i did recreate the application with the screen shown above but the folder is not visible in roon
Please post a screenshot of Container Station showing the actual Compose file used then. How to get that screen I described above.
ignore and thanks for the support, it looks like the folder was listed just needed adding to the watchlist
1 Like
The configurator tool doesn’t necessarily do anything “special” for Roon other than add some defaults. Once you have generated the compose file you are welcome to edit that in the future instead. I did add a share link so that people can share their configuration but it can also be used to “save” your configuration if you want to edit it later.
First time container user here too and i had the same problem with the not seeing my music library.
For me, the issue was with instruction step 2: In Volumes, leave the default entries as they are unless you need to add more folders. The default is “/share/Music:/Music”. If i understand correctly, this maps the Qnap directory Music to the container directory Music.
In my setup, my music files are actually in the directory “Media/My Music”. So in step 2, i changed the default from “/share/Music:/Music” to ““/share/Media/My music:/Music” and my library is now found in Roon.
Ps. Additional info in case it helps: I didn’t try to use the restore functionality. I deleted the old (non container) Roon application from the QNAP NAS. I downloaded and uploaded the YML file rather than using the copy and paste.
1 Like
First time container user, too, and I also cannot see my music library. Some month ago, in a manual backup step, I have made screenshots of each screen in roon→settings. I now have compared these screenshots with the new roon running in docker. The only difference seems to be in settings → storage. I can confirm that the QNAP path definitely is the same.
-
Roon now shows two paths “Music Folder” and “QNAP”. Not sure is this is normal because of container-solution or if this is a problem.
-
The Music folder is disabled. Not clear why.
-
The QNAP-path is told to be not available (see error message).
Also not clear why. Certainly the logon in general settings is ok.
Do you have any proposal how provide the music folder to roon in the container.
Hello, I’d like to create the /Container path on my USB SSD drive. How / when can I choose this drive? It’s the first time I’m using Container Station.
Thanks!
@Francesco_Serrano /Container folder created and used by Container Station, and /Roon path bearing the actual running container (including roon´s database, that is why it is performance-sensitive) are actually two different things. You can leave Container station and its /Container folder on the main volume.
If you want to run the roon container externally, you need to format the external USB drive as EXT4 volume (exFAT or FAT32 would not do!), create the necessary /roon/ folder in there, and then add the exact volume name to the share path, as if it was a top-level folder name of an internal volume.
Example: Your drive is by the name MYUSBSTICK, then the path in container generator should read something like:
/share/MYUSBSTICK/roon:/Roon
I have successfully done that, and roon runs smooth in a container on an external drive with the /music/ share pointing to the internal volumes.
1 Like
It is two separated things: “Music Folder” is the new main path you have allowed to be shared with the container, and should point to your main music storage inside the NAS (whatever its hierarchy and name is, only you can know). The /QNAP…/ storage is a remnant of the old, obsolete path used by RoonOnNAS, and appears solely as a result of restoring the backup.
Enable the “Music Folder” storage, just to try if it is pointing to the right folder. If yes, you should see roon start recognizing tracks in there. If that is the case, you can delete the old QNAP path, as it will help roon to know that albums under the new “Music Folder” are actually albums being moved over from the old, non-existent path.
Depends on where your music is stored, i.e. top-level folder name and hierarchy. If you use the /Multimedia/ top-folder which many QNAP NAS have from the start, and a subfolder named /Music/, the line in the docker generator should read like:
/share/Multimedia/Music:/Music
If it is not working, feel free to share a screenshot of your volumes, top-level folders and music folder in File Station.
Hello Arindal, thank you for your help. I have enabled the /Music Folder and it has started importing the tracks. I did not dare to do so on my own for I was not sure what it really means to enable it.
By the way, Roon also indicated that a software update is available, but I think for the year 2026 I will not import any Roon-updates any more ….
1 Like
If you plan to run a database backup restore, I recommend to do this first, then deleting all obsolete storage paths of the past, and only then enabling the new Music Folder as a storage. With my setup, it helped roon identifying the albums correctly.
This is probably today’s Roon 2.66 (Build 1657/1658), which is said to offer only performance improvements, so don´t worry! Anyways, it is good to run a test if roon can self-update within the container.
I also encountered this error log and haven’t resolved it yet. I plan to try the method suggested by AI tonight.
Hi,
Indeed Roon indicated that a software update is available.
How do I install this update? Can I just do it the way I used to before I started using Container Station?
It should work that way, yes, you confirm in Roon Remote that you accept the update that was offered.