Hey @David_Small2,
Thanks for writing in! From a fresh Roon Server diagnostic report, we can see what’s happening. Inside the container, /Music isn’t mounted to your NAS at all; it’s come up as a 16 MB temporary RAM disk, which is what Container Station does when the host path in the compose file doesn’t exist. Your /Roon and /RoonBackups mappings are attached correctly, so it’s just this one line.
The culprit is the path /share/Music. Linux is case-sensitive, and your folder is named MUSIC, so /share/Music doesn’t exist on the NAS.
To confirm the exact path, enable SSH on the NAS (Control Panel → Telnet/SSH), connect, and run:
ls -la /share/ | grep -i music
You’ll see either MUSIC directly, or a symlink like MUSIC -> CACHEDEV2_DATA/MUSIC. Use whichever full path that shows, for a share on Volume 2 it’s usually /share/CACHEDEV2_DATA/MUSIC.
Then update your compose to:
volumes:
- /share/Container/roon:/Roon
- /share/CACHEDEV2_DATA/MUSIC:/Music
- /share/Container/roon-backups:/RoonBackups
(substituting the path you confirmed above)
Note that Container Station can’t change volume mappings on a running container, you’ll need to stop and remove the existing one and re-create it from the edited compose file. Your database lives in /share/Container/roon, so nothing is lost.
Once it’s back up, go to Settings → Storage in Roon. The existing “Music Folder” entry pointing at /Music should come online and start importing on its own. If it doesn’t, remove it and re-add /Music.
We’ll be monitoring for your reply, thank you!