I really appreciate your contribution, along with other members on this thread, who are helping people navigate this new challenge created by the upcoming changes. Unfortunately, some selfish individuals will always try to derail the main purpose or put a negative spin on things.
1 Like
“If I’m the man, himself”…..not sure who you think I am. 
Yes, I do run the RoonOnNas QNAP package and outside of some operational glitches along the way, it’s worked pretty well. The 1688x is getting long in the tooth in terms of specs (10th gen Intel Xeon) but for a NAS, it has more than enough horsepower. I bought it to consolidate a bunch of things I wanted to do including retiring an ancient Dell PowerEdge server I was using as a Windows Server (in a Mac household, it’s useful to have a Windows instance somewhere). My 1688x has 96 GB of RAM and twelve 16TB drives in a RAID 6 array. The SSD slots are 4 x 1 TB Ironwolf SSD which was what I could afford four years ago (configured for RAID 5). The OS and all apps live here, as well as Roon and and the Roon database. There are also two M.2 1 TB SSDs for ZFS cache.
In my house, I have four different music zones (three multichannel zones, one 2-channel). RoPieee on Raspberry Pis are two Roon endpoints for DACs, another is a Oppo 203 and the last is just Airplay. And of course, playing Roon through iPhone/iPads are a thing too.
Part of selecting a QNAP NAS in the first place was getting ZFS from a supported vendor where at this stage in my life, I just didn’t want to go the route you did and build my own. I certainly have the technical chops, but not the time. ZFS has been pretty bulletproof on data security, even with power outages or forced reboots (a thing I had to do a fair amount in the early days of QuTS Hero 5.0).
I run a few Docker containers in Container Station (and I have Portainer installed as well). So I can easily migrate over to a Roon container with a little guidance. And if that is the supported way forward, then I’m willing to help in the process. If someone is willing to share the early documentation, I can certainly verify that it works on my end and offer feedback. And I’m assuming that the update process inside the container would adhere to the normal Roon update process and the container would just need to be pointed to the existing RoonDatabase shared directory.
DM me if you want to include me in this little exercise.
I’m still working on options for QNAP users. The docker image is definitely one way to go if you want to shift in that direction. I’m hoping we might have yet another solution for QNAP users this coming week.
2 Likes
Looking forward to the choices. Let me know.
When can we expect to see the “officially supported” Early Access version of the Docker container posted?
That happened last week:
5 Likes
Nice, thanks! I assume eventually the Docker image will have a Production (vs. Early Access) release?
Yes, that’s the standard process.
1 Like
This is already available:
I have the production image running based on the corresponding docker-compose.yml.
Yes, you can do that, but the Docker solution itself is still in EA, and presumably has not been tested with the Production build it is pulling to use inside the container, so caveat emptor…
1 Like
The image hasn’t been explicitly tested with production; however, I don’t believe you should have any problems with either production or early access.
I do have a set of smoke and runtime tests that I ran against every change on both the production and early access version.
Edit:
It probably isn’t fair to say that it wasn’t tested against production. Also the container I’ve been running most recently on my NAS is the 2.64 version in the container.
2 Likes
Since some days I am running this image with production without problems. On the contrary, the performance is very good I must say.
I’m going to ask a really dumb question. I’ve setup the docker application on my 1688x and it launches. The Roon clients see it. But it is pretty much a virgin install. So I feel I didn’t get the path to the folder correct, or am I supposed to do that at all? Will this docker release just assume everything the RoonOnNas release did if I point it to the RoonServer directory or does it need to be a new directory and I just restore the server from the previous backup folder?
Does anyone know what time today the update is dropping? Very keen to see if the claimed “significantly reduced memory usage” is actually true.
1 Like
People in Early Access have been looking at the memory
Equally keen to know when the uodate will drop.
3 Likes
Well it’s coming up to 18:00 here in the UK and the update’s still not out yet. Maybe 18:00 will be the magic number. Tick tock.
19:00 now and still no sign. Do you think it was an April Fool?
Some discussion here:
There’s another 10 eastern time hours before tomorrow.
1 Like