QNAP QTS does not support new minimum system requirements to run Roon Server (20 April 2026)

[Glimmer]

@Stephen_Shaw1

NOTE: I’m actively testing the docker image on my personal QNAP NAS. I haven’t tested going from the installed Roon QNAP package to the docker image yet, but testing the image so far has worked fairly well on my old QNAP and has been fairly easy and straightforward. Hopefully more details and an initial image will be available this coming week for anyone that wants to give it a try.

This was posted by Roon Staff

[mjw (Father! Father! Resist not! Let us destroy the core! Set us free!)]

@Andreas_Scheunemann

…a docker solution was not required or recommend when I first set up my system.

This has changed. A Docker image will be officially supported and maintained by Roon.

@Andreas_Scheunemann

And it adds another supplier in the solution built with all associated implications, e.g. compatibility in case of SW upgrades from Roon, QNAP or docker.

No, it does not. Roon will support the container, i.e., Roon will update according to your automatic update preferences, and Docker is supported by QNAP.

[Moonshiner (Thomas)]

You can still run Roon from your QNAP (even if QNAP dont update their glibc verison) by using the docker image that will be released.

[Stephen_Shaw1 (Stephen Shaw)]

I think it is worth noting too that with a docker image we can isolate our requirements from the platform. As long as a platform supports some form of containerization then we are not restricted by their platform and versions. For example, with docker we no longer care what the version of glibc QNAP ships which means if we are in a position where we need to bump glibc and QNAP decides to go another decade+ of not updating their dependencies we are isolated from that.

Containers/docker/etc are a huge part of the tech industry now that it is everywhere now.

[Stephen_Shaw1 (Stephen Shaw)]

For now, we are going to host them on github, but long term that might change. Hopefully we’ll open this up very soon: https://github.com/RoonLabs/roon-docker

[Gianluca_Finistauri]

Super. My suggestion: make it the easiest possible. Me - and possibly many others - don’t even know what github is.

I need a link for a download and super clear step-by-step instructions to install it from my QNap Web interface.

Will the passage to the Docker imply a migration to a new Roon Core, requiring a migration of Roon library & files? (incl. re-address of storage, etc.)

thanks

[David_Broughton]

@Andreas_Scheunemann Thank you! My sentiments exactly! I’m a less technical user, and I just want my QNAP to operate as it has until now with Roon using it’s native platform designed to be run with Roon.

[Andreas_Scheunemann]

Hi, are you a member of Roon staff? You are stating what Roon is going to do regarding the release and maintenance of the docker solution which I would expect Roon to publish.

[mjw (Father! Father! Resist not! Let us destroy the core! Set us free!)]

No, I am a volunteer moderator.

I am reiterating what Roon has already said, and what you can read for yourself in this forum.

[Rugby (aka Daniel or Big Dan)]

@Gianluca_Finistauri

requiring a migration of Roon library & files?

I would imagine it would require a backup of the older server installation and then a restore of the database into the new server installation.

[gTunes]

@Rugby

I would imagine it would require a backup of the older server installation and then a restore of the database into the new server installation.

I personally think this is the right approach.

I wrote a walkthrough (five years ago!) on how to run Roon in Docker on Synology. In the walkthrough, I proposed a folder structure for container-based Roon and suggested that the first step was to get existing Roon backups copied over to that folder. One way or another, you need to get existing backups to be visible to the container and this seemed like the simplest path.

I wrote the walkthrough before Synology supported compose files (which is what they call “Projects”). It’s tempting to think about moving from the wizard-based configuration over to Projects, but there are tradeoffs. If the new container requires or prefers image updates for app updates, then it’s probably better to stick with the single-container wizard approach because Synology is much better with image updates when not using Projects (individual containers get update notifications and single-click updates, Projects get no notifications and a complex, multi-step update process).

I’m hopeful that we’ll get great guides from Roon on how to get containers stood up on Synology and QNAP as well as how to update images. Until then, my old guide is probably a pretty good reference for how to do it on Synology:

Walkthrough : Roon in a Docker container on Synology DSM 7

Hi, folks. Synology recently released a DSM upgrade which introduced compatibility problems with the Roon package a number of community members, including me, run. I’m using this opportunity to switch to running Roon in a Docker container. I put together this walkthrough to hopefully help anyone else considering going down the same path. This walkthrough utilizes the container image produced by @Steef_de_Bruijn, who I want to thank for his work. That work made this possible, and it’s sincerely…

[David_Broughton]

@Stephen_Shaw1 QNAP was my preferred choice because it is fanless. I don’t have a basement for a noisy NAS, and Roon Nucleus is not available in my country. My QNAP is my Roon server (core), and all my music ripped and downloaded is stored on it. This is why I’m anxious about the latest developments on new Roon system requirements.

[Stephen_Shaw1 (Stephen Shaw)]

That makes a lot of sense. I have a QNAP at home, so I’m actively testing things on it. Stay tuned

[Andreas_Scheunemann]

@mjw

I am reiterating what Roon has already said, and what you can read for yourself in this forum

I really appreciate your engagement to support Roon users, it‘s good to have experts like you available who spend their time helping out.

Can you please direct me to the related statement from Roon staff where they:

• stated that they are providing an approved docker solution
• provided an expected release date of the officially released solution
• committed to maintain it.

So far I have not seen all above in this thread, but maybe there is another relevant thread which I am not aware of.

Many thanks

[Carl]

Hi @Andreas_Scheunemann,

Check out this pinned official topic from Roon …. It was also linked to in the 2nd post of this topic.

Important: Roon Minimum System Requirements Are Changing on April 20, 2026

On April 20, 2026, we’ll release a new version of Roon … Roon Server Roon [GUI] Roon Bridge … that brings performance improvements and significantly reduced memory usage. However, it will not be compatible with a small number of older systems. What minimum system requirements are changing? Starting with this release on April 20th, 2026: Roon on macOS will require macOS 12 (Monterey) or later Roon on Linux will require glibc 2.27 or later and OpenSSL 1.1.1 How can I check I am impact…

Specifically this section…

@vova

What if I can’t update my Linux computer or NAS?

• Run RoonServer via Docker - Docker is an operating system-level virtualization technology that will let you run a newer set of software on top of your older operating system. We are launching an official supported Docker image for RoonServer. Early access users will get it first, with a production release shortly after.

[Rugby (aka Daniel or Big Dan)]

It seems the TBS-464 can run QuTS hero 5.2.9 which I believe is using the later libc. If that is the case you could you upgrade your NAS’ OS?

It will of course mean tearing down your RAID, resetting the NAS from scratch and then setting everything back up in this case.

As an aside, that NAS does not have upgrade able RAM. As your library grows, or Roon requirements grow, or other RAM pressures increase, you might find that you will need to move the RoonServer off the NAS anyway.

[gTunes]

This seems akin to tearing down and rebuilding your house because you found a leaking faucet.

I suspect moving to a Docker-based installation of Roon will be a non-event for most people. Maybe 15 minutes of work, and very low risk. Copying everything off of your NAS, installing a new operating system, getting everything re-configured, and getting your data copied back is hours of work at least and you run the risk that your NAS won’t perform well with the new OS.

Docker may sound scary to people because it’s a thing they’re not familiar with. In practice, it’s going to be quite simple for most people to get it set up and to get back to parity with what they have now.

It’s probably very wise to just wait and see what Roon’s guidance is once an image and documentation is available. @Stephen_Shaw1 says that will be soon.

[Stephen_Shaw1 (Stephen Shaw)]

Hey everyone!

Today I ended up being distracted by a marginally larger fire at work which unfortunately prevented me from wrapping up some docker stuff. Also, we have been having meetings about docker, NAS, etc with this new EA.

I small update…

We have decided to pivot slightly. First, we are still doing the docker image and I’m really hoping to have it out (my) tomorrow since it is late for me right now. Also, I think we might have a much better option/solution for those on QNAP. Please stay tuned, but we are hoping to have some more details soon.

[Stephen_Shaw1 (Stephen Shaw)]

Hey, I’m actively working on solutions that include an approved docker solution that I’m trying really hard to get at least an EA version out [tomorrow]

The goal is to make the image and dockerfile public so that we can share what we are doing publicly and the community can also help contribute to. I’m working some more on it this evening and hoping to have it available very soon. I originally was really hoping to have it available at the beginning of the week, but sometimes the best laid plans fall apart a bit. I’ve pivoted slightly on how I’m building the image and discovered some cool things for others too. I’m really hoping that all of this will benefit the community and that it’ll make everyone’s life easier going forward. (ie, hopefully no more surprises like this for us or our awesome users )

[David_Broughton]

@Stephen_Shaw1 Thank you. Hope all is going to work fine without problems.