For what it’s worth, I am with @gTunes in my support of official Docker images.
Also, my research has led me to believe that folks on DSM 7.2 and later should be fine, but DSM 7.0–7.1 will be on glibc 2.26, and DSM 6 users will be on 2.20, which sounds like put BOTH groups in the SOL category.
As @gtunes stated, just make official Docker images and be done with it. This will be good for MANY purposes.
Hey everyone!
I’ll do my best to answer all the questions here, but if I miss something, please don’t hesitate to ask again.
First, I want to be upfront: breaking NAS devices was absolutely not the intention and I’m really sorry about the problems and frustration that it has caused. The motivation behind upgrading to .NET 10 was that it brings some meaningful out-of-the-box performance improvements and sets us up for faster progress on features and quality of life improvements down the road. I’m genuinely excited about what it will unlock.
That said, the current EA build breaking various NAS devices (notably QNAP and Synology) is on me. When I did the .NET 10 migration work, I didn’t fully account for the glibc version requirements that come along with it. I’ve spent most of the past week or so since the EA release, which is on hold, digging into the problem and exploring what the options look like.
On the QNAP situation specifically — I don’t have any inside knowledge about QuTS Hero 6.0 or any upcoming QTS releases. What I shared was based on QNAP’s own website and some community speculation. It’s really unfortunate that glibc hasn’t been updated in over a decade.
As for Docker… I can’t confirm or deny that I’ve been working on something, but I hope to have more to share very soon. 
Thanks for being patient with me.
Well thanks for that. And please don’t overlook what I suggested about this community. Our willingness to collaborate never seems to be honored regularly enough. I am all for the .NET 10 upgrade, which appears should run fine in current Synology devices OR in Docker. Either way, I am fine. I just want to encourage more openness and collaboration between Roon staffers and this community than seems to generally occur…
I am glad that you are sensitive to the issues with QNAP users and perhaps older Synology users, but I do believe that a supported Docker option would make the most sense for everyone moving forward. It will be a bit much for certain demographics to handle, but there are other options for those folks.
This is a fantastic response, @Stephen.
Purely hypothetically - if an investigation into Docker were to be underway, I’d like to vote for “experimental” or “unsupported” containers to be made available sooner rather than later. There’s enough prior art kicking around for me to believe that it won’t be too tough to get containers up and running but it’s worth it to let us play with anything for a while before it moves to “supported” or “official”. I hope there’s no reason to think that an experimental container should be running EA bits. Many of us see EA as a congealed bowl of spaghetti such that if you pull on one noodle, you get the whole thing (clients included). So we stay on prod.
I made a comment earlier about custom PUID/PGID. That was an error. I’ve looked at my own container setup and it doesn’t support it. Roon runs as root. That’s ok but I hope you, hypothetically of course, consider one of the existing strategies for allowing the specification of a user (PUID/PGID or, better yet, one of the rootless options).
Thanks again for your response!
@DDPS I can’t make promises beyond myself in improving engagement with the community, but I’ll see what I can do.
@gTunes Thanks, I’ll definitely keep this in mind!
@Stephen that would be wonderful. A lot of people here would be willing to collaborate and cooperate. I am among them. Thanks.
Ok, it is “official” that I’m working on an Official Roon Server docker image 
Yes, congratulations to you. I just posted this as well in an effort to be helpful in the Roon Software Discussion > QNAP/Synology NAS section:
Hi,
I’m running a DS218+ with DSM 7.2.2-72806 Update 5. Roon is running through RoonOnNas.
When i ssh into my synology there is no
/lib/libc.so.6
The ldd --version command doesn’t work as well.
So I don’t have glibc at all? Is there a way to install it?
Thanks
You should be able to simply type /lib/libc.so.6 at the command line, and you should see version 2.36 for Synology DSM 7.2.
What happens when you type that command?
GNU C Library (GNU libc) stable release version 2.36.
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 12.2.0.
libc ABIs: UNIQUE IFUNC ABSOLUTE
Minimum supported kernel: 3.2.0
For bug reporting instructions, please see:
<https://www.gnu.org/software/libc/bugs.html>.
Thank you! Think I’m fine.
You are indeed!
Can I assume that I don’t have to update Roon so I can continue to run the current release on my QNAP NAS? Unless you guys can provide a workaround for us QNAP users stuck with nd old glibc version.
The workaround is to install Roon using the docker installation that they will provide.
you can opt out of updating, but I’m sure at one point in the future you will want to get access to new features and bug fixes.
Question is, if that is retaining all the connectivity options, a QNAP machine is offering, notably USB-Out and HDMI.
It’s all in the announcement post:
As @Arindal says,
but maybe you don’t even need this.
There is ongoing discussion in:
Fortunately, with the help of Claude AI I set up Docker on my Synology 918+ the other month as I was restricted by having it on my PC. Now everyone can use Roon 24/7 without needing my PC on.
Today Claude has confirmed I’ll be OK but it may take Docker a day or two to update and has given me a plan of what I will need to do. If you haven’t set up docker yet you may want to wait until after the update but it took me a while initially so you may want to practice.
Good luck all.
Update: I just read the whole thread and see a Roon Docker version will be made available. Wait and see I guess.