# Roon Server on QNAP NAS

**URL:** <https://community.roonlabs.com/t/roon-server-on-qnap-nas/320144>\
**Category:** QNAP/Synology NAS\
**Created:** [May 12, 2026, 3:08pm UTC](https://community.roonlabs.com/t/roon-server-on-qnap-nas/320144 "2026-05-12T15:08:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andreas\_Neiss](https://community.roonlabs.com/letter_avatar/andreas_neiss/32/5_5575768a8748004e209b776fc1b2916d.png) [@Andreas\_Neiss](https://community.roonlabs.com/u/Andreas_Neiss)\
**Post date:** [May 12, 2026, 3:08pm UTC](https://community.roonlabs.com/t/roon-server-on-qnap-nas/320144/1 "2026-05-12T15:08:51Z")

</div>

Hello!

I’m using Roon Server on NAS on a QNAP TVS 472 XT NAS. For the last update, I had to install Roon via a Docker container (Container Station). Since I’m not an IT expert, this was very time-consuming.

Now there’s a new version of Roon Server. It suggests deleting the old Docker container and installing Roon using a new one. This means rebuilding the entire Roon database.

If Roon doesn’t offer a simpler solution for Roon on NAS in the coming months, I’ll abandon Roon and go back to JRiver Media Center.

The only real advantage of Roon is controlling devices; everything else (like genres) is, in my opinion, suboptimal because you can’t import genres from JRiver. JRiver uses Music Styles, and Roon’s genres are unfortunately unusable.

I hope Roon offers a solution for Roon on NAS for QNAP NAS soon; otherwise, I’ll cancel my subscription.

---

<div class="post-metadata">

**Author:** ![Suedkiez](https://community.roonlabs.com/user_avatar/community.roonlabs.com/suedkiez/32/107321_2.png) [@Suedkiez](https://community.roonlabs.com/u/Suedkiez)\
**Post date:** [May 12, 2026, 3:21pm UTC](https://community.roonlabs.com/t/roon-server-on-qnap-nas/320144/2 "2026-05-12T15:21:32Z")

</div>

> [@Andreas\_Neiss](#):
>
> Now there’s a new version of Roon Server. It suggests deleting the old Docker container and installing Roon using a new one.

Where does it suggest that? As far as I know, updates for Roon are downloaded and installed _within_ the container.

In fact, the new release notes specifically refer to „in-container upgrades“

> [@Roon 2.66 and ARC 1.78 are Live!](https://community.roonlabs.com/t/roon-2-66-and-arc-1-78-are-live/319651/1):
>
> For Linux and Docker users, we addressed an issue where in-container upgrades could fail on some hosts with more restrictive file permissions.

---

<div class="post-metadata">

**Author:** ![DDPS](https://community.roonlabs.com/user_avatar/community.roonlabs.com/ddps/32/162722_2.png) [@DDPS](https://community.roonlabs.com/u/DDPS)\
**Post date:** [May 13, 2026, 12:22am UTC](https://community.roonlabs.com/t/roon-server-on-qnap-nas/320144/3 "2026-05-13T00:22:03Z")

</div>

@Suedkiez is correct. The Roon software is not part of the container package. The Docker container downloads and installs Roon in your designated /Roon mapping. Once you’ve set up the Docker container and got everything running, Roon updates itself in-place just like the NAS package always did.