That’s great to hear! I’m glad it worked!
I had the same issue when upgrading to DSM 7 on my DS1019+, which was fixed by the Shell Script suggestion at runtime.
I notice though now that the NAS is using more RAM that before - which I assume is because of the increased parameters in the shell script? Is the 204800 reference adjustable, and hence may be lowered to reduce RAM use?
Forgive me, but i’m a UNIX n00b 
Thanks in advance
I don’t understand the implementation of file watching enough to understand how memory usage works. In the script I provided, 204800 is an arbitrary choice. It specifies the number of files to watch. Depending on how many files and folders you have (I’m guessing that it is both files and folders), you may actually need to adjust it up or you opt to adjust it down. Whether memory usage is fixed or is proportional to the actual number of files you have up to the specified max, I can’t say.
Personally, I’d focus on getting the behavior correct and not worry about memory usage unless you believe that your NAS is under memory pressure and is experiencing symptoms as a result.
Thanks Greg - really helpful and speedy reply!
My needs are fairly simple - the NAS runs Roon Core, Plex, Time Machine Backups and one Windows VM for occasional use (i’m Mac-based), and the VM can no longer run as there’s not enough memory.
It’s an 8GB NAS which was fine, and it could run the VM under DSM 7 previously, so I think / assume it’s the script I added today.
I’ll try adjusting the number / removing the script and see if I can figure out if it’s linked. There’s possibly a few knock-ons from he DSM 7 upgrade I did about a month ago i’m only just finding.
But … THANK-YOU for your time, generosity and expertise!
My Synology NAS is asking me to update…
But provides the following Update Message…
Is it safe to upgrade to this version of DSM?
I’m running Roon in docker and on the latest DSM without any problems.
Thanks. I’ll upgrade then.
DId docker run better than natively on DSM 7 Ramon_Laponder?
I have it native currently, but wonder if the docker version runs better since its likely just Roon ROCK in that docker image.
I was thinking the same thing, but knowing nothing about the technology i didn’t use it to remove that layer of doubt.
personally i do not see any difference. The part that i like more is that I also have a docker running with “watchtower” this keeps my roon docker updated as soon as there is a new version. That way it stays as current as possible.
Well, roon auto updates also. And likely sooner than the docker image gets recompiled and uploaded. So not sure about that.
Yes that is correct. Roon updates itself in the docker, but the docker image is also being updated from time to time (not very often though)
I just removed my SSD that had roon DB and moved it to a docker image on a 3 disk RAID5 WD Red’s. It’s slightly slower to search, but honestly can hardly notice it. 12k tracks, 2500 albums DB. Runs fine.
Will get SSD cache sometime soon though anyway.
Just wanted to say a big thank you to Greg and Steef.
Installed painlessly on DSM 7.1
I did notice the order of things might have changed since the original post- some of the screenshots seem different? But it’s exactly the same settings that need to be applied so all good.
I’m on a DS218+ with only the base 2Gb of ram streaming Qobuz and all is good. Just going to try streaming a local ripped file …I’m not expecting it to work as my music folder is on a Red NAS drive not SSD.
Edit: streaming ripped CD’s works just fine!
1 Like
is there any advantage to running roon on a docker container instead of running it as a native synology app ?
I personally don’t think so. I think using Docker would make it simply use more RAM.
I don’t have an opinion on which approach you should take. I use the Docker approach because I like the encapsulation and the insulation from Synology changes, which have caused issues with packages in the past. In my case, Docker also simplifies permission management because you aren’t granting a package/package user permission to your library directories, you’re just mapping them using Docker.
For reference, Docker currently shows my Roon container using 847mb. There may be unrepresented memory usage by Docker itself but, since I also run HomeBridge in a container, that usage is probably amortized.
There’s no right answer here - if you are memory constrained or have a lower-powered NAS, the package might be better. If those aren’t issues, Docker has its advantages. Perhaps try Docker first and, if you don’t like it, switch the package. The package will potentially leave more cruft behind than the Docker approach, which is why I advise trying it second.
2 Likes
Hello
Thanks for these detailed instructions, I’ve been going crazy since DSM 7 and roon not working.
I have an issue though, I complete all the steps and then the container will keep stopping. Extract from the log as follows:
Can anyone please help as to what the issue might be?
I’m using an SSD USB for the docker folder, which has worked fine previously using RoononNas for Synology (my model is DS218+)
Thanks
Hi I think this has to do with dsm7 not supporting usb. This can be fixed using this info here:
https://mariushosting.com/synology-how-to-add-usb-support-on-dsm-7/
Thank you for the advice Ramon.
The USB SSD is recognized under external devices before trying the fix, and I tried the fix you suggested and I still can’t get the container to run, although the log file error has now changed to the following:
I tried using my hard drives in the NAS for the docker shared folder and get the same log file error.
Any further ideas?
Thanks