I think it’s more a question to QNAP if they should not update their system and support glibc 2.27 (or newer)
Judging by the comments (and myself) the new version is much snappier and use less system resources - and I don’t think its fair that Roon holds back on such an improvement just because QNAP don’t update their systems.
Yes, glibc 2.21 used by QNAP was released over a decade ago.
The recent changes, which resulted in some ageing systems no longer having support, has brought about welcome performance improvements to everyone else.
The decision to support Docker container is a fantastic addition, and means older hardware can now continue to run Roon.
However, if anyone is struggling with Docker/Container Station, please open a Support request rather than posting here.
Hi, mjw,
I didn’t come here asking for your opinion about how great Docker is.
I paid for Roon and it worked perfectly on my QNAP until Roon decided to break it with a forced update. Now the only “solution” you people offer is Docker, which most normal users don’t know how to use.
I’m not a developer, I’m a customer. Telling people “just use Docker or open a ticket” after you broke a paid product is not customer support, it’s arrogance.
Many long-time users are ■■■■■■ off with this attitude, and for good reason.
Just that the NAS apps were a community project from a single member and not part of the paid Roon software experience. See also the following statement from the maintainer:
As of today no more Roon on our Qnap NAS after 2.65 was offered and installed - not happy.
Why is it even offered to go to 2.65 when Roon sees that the server software runs on a Qnap NAS? As it cannot work it should not be offered or am I missing something obvious?
In any case no time to deal with Docker right now so it would be cool if Roon was offering a download link to a QPKG file of 2.64. That should be good enough to tide users over until they can make the switch and move to Docker but it seems that such a link does not yet exist?
The Roon software never was part of the NAS packages (not included, not allowed to distribute). It got downloaded once on installation/first run of the NAS package. So you’re free to grab a new copy of the NAS package but it will not change anything as Roon is not part of it.
Hi,
I really don’t understand Roon’s approach here.
You clearly warned Mac users that version 2.65 wouldn’t work on Catalina, which was the right thing to do. But with QNAP NAS you did exactly the opposite: you knew most QNAP systems use very old libraries (glibc 2.21 from 2015), you knew the update would break them, and yet you offered the update with zero warning.
No message, no “this update is not compatible with QNAP”, nothing.
Now we’re left with a paid product that doesn’t work and no way to go back to the previous version. That’s not how you should treat long-time customers.
At minimum, users deserved a clear warning before the update was pushed.
If you think blowing up the thread will get you a result, then have at it but no one will be willing to help
Roon app was/is available in the QNAP App Center, and supposedly the Asustor App Store as well. It does appear to be an officially supported app, so I understand people who are frustrated that it does not work anymore.
I sincerely hope, Roonlabs will issue a ´last 2.64 version´, as they did for Mac users. For those QNAP users, who are willing to invest a minimum of time, I recommend running Roon 2.65 under Container Station. Despite from some tinkering with folder/share paths, it is really easy to install, and does not require deeper knowledge.
If anyone needs help with docker on QNAP, I suggest to open a thread accumulating useful information. Can offer my help from the perspective of a non-Linux guy.
There was plenty of warnings given about this change imo.
Sticky message on the forum and email from Roon.
Im not sure if Roon have the ability to give in app messages, if not I think that is a future improvement they could make when they are rolling out significant changes.
It makes more sense to approach QNAP and ask them to update their system. This new Roon version is a huge improvement and it’s not fair for everyone else if Roon have to hold back such development and improvement just because QNAP run with an old glibc version
In defense of Roon on this one, on April 2, they warned QNAP users in the same breath/post that they warned Mac users.
Roon Labs posted this 26 days ago - and I think was a pinned topic:
It was also in the April newsletter sent out on the 3rd of April, and Roon Labs said that they had sent out an in-app announcement to affected customers - although I believe that not everyone received it, possibly because Roon Labs data on customer systems was not 100% accurate.
All this is very well, but what do we do now? Roon is dead for us and we don’t have the computer knowledge to understand this docker stuff.
I understood we wouldn’t be offered an upgrade we couldn’t use, it just wouldn’t upload…
If I’m wrong about that, ok. But what do we do now to get even the older Roon back.
If you figure out the exact path where your music is stored (feel free to share a screenshot from File Station showing volume/folder hierarchy), plus a folder for extracting/running the container on an SSD volume (for example the path you used to choose as a database location in RoonOnNas), it is fairly easy. Container Station is straightforward, and the docker generator for QNAP contains the important options.
If I were you I would create a support ticket and let them know you need assistance setting up docker on your system.
It’s not that difficult, but I understand it can seem like voodoo magic if you have not tinkered with it before.
Thanks, but I can’t even open Container station. It tells me to go back to the App Store and open it. I have, many times, still nothing. Just rebooting NAS now to see if it helps
It didn’t help…
Hi, can I migrate my MAC to Roon 2.65 but remain on version 2.64 on my QNAP NAS or later on the QNAP NAS docker version?
I think so, but I’m far from sure. MAC is in this case only the remote and not server. But,’ someone with more technical insight should confirm
You have posted in a community discussion thread, and, as you said, Docker is the only way to run Roon on your QNAP. Since Roon support staff do not monitor this category, I signposted Support, so you may receive appropriate and timely assistance.
I get that it is frustrating, but that is no reason to be rude to community members and Roon customers, like myself, who are trying to help out.
If you want Roon to learn about your dissatisfaction, please post in Feedback since Roon monitors that category, but not Roon Software Discussion.