# Roon Server Update Fails on QNAP Container - Stuck at 2.71 (ref#0U5DH2) **URL:** \ **Category:** Support\ **Tags:** rctt\_-02-1\ **Created:** [September 15, 2026, 9:13pm UTC](https://community.roonlabs.com/t/roon-server-update-fails-on-qnap-container-stuck-at-2-71-ref-0u5dh2/324956 "2026-09-15T21:13:12Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![PapaSoul](https://community.roonlabs.com/user_avatar/community.roonlabs.com/papasoul/32/99198_2.png) [@PapaSoul](https://community.roonlabs.com/u/PapaSoul)\ **Post date:** [September 15, 2026, 9:13pm UTC](https://community.roonlabs.com/t/roon-server-update-fails-on-qnap-container-stuck-at-2-71-ref-0u5dh2/324956/1 "2026-09-15T21:13:12Z")
#### Hi! What’s not quite right with Roon? · None of the above quite fits #### None of the above quite fits · None of these quite match #### Tell us what's going on · Hello - My Roon Server will not update past 2.71 (build 1680) Roon Server is running in QNAP Container station. I get notified with pop-up on every Roon client that updates are ready. I see in the About page of the Roon client that Roon Server has an update ready. When I click to install, the update downloads and then fails. I read multiple posts on this same problem but there was no clear resolution. I redeployed the Roon Server app using the latest docker image as of Sep 15. Problem still occurs. #### Tell us about your home network · Hello - My Roon Server will not update past 2.71 (build 1680) Roon Server is running in QNAP Container station. I get notified with pop-up on every Roon client that updates are ready. I see in the About page of the Roon client that Roon Server has an update ready. When I click to install, the update downloads and then fails. I read multiple posts on this same problem but there was no clear resolution. I redeployed the Roon Server app using the latest docker image as of Sep 15. Problem still occurs. OKJ THIS INFINITE SCROLL FORM SUCKS!!! ---
**Author:** ![BlackJack](https://community.roonlabs.com/user_avatar/community.roonlabs.com/blackjack/32/39743_2.png) [@BlackJack](https://community.roonlabs.com/u/BlackJack)\ **Post date:** [September 15, 2026, 9:21pm UTC](https://community.roonlabs.com/t/roon-server-update-fails-on-qnap-container-stuck-at-2-71-ref-0u5dh2/324956/2 "2026-09-15T21:21:47Z")
AFAIK is there a clear solution. Use the docker image v1.0.8 or newer. > [@PapaSoul](#): > > using the latest docker image as of Sep 15. Problem still occurs. So you went to the image tab and pulled a new version? ---
**Author:** ![PapaSoul](https://community.roonlabs.com/user_avatar/community.roonlabs.com/papasoul/32/99198_2.png) [@PapaSoul](https://community.roonlabs.com/u/PapaSoul)\ **Post date:** [September 15, 2026, 9:47pm UTC](https://community.roonlabs.com/t/roon-server-update-fails-on-qnap-container-stuck-at-2-71-ref-0u5dh2/324956/3 "2026-09-15T21:47:05Z")
\> AFAIK is there a clear solution. Use the docker image v1.0.8 or newer. Please point me to the kb article. \>Pulled a new version In Container Station on the QNAP, I used the “Recreate” option which uses the line in the YAML code “`image: ``ghcr.io/roonlabs/roonserver:latest`” which specifies the latest image. Is there a different method? I’m no stranger to Docker and manage multiple containers, but I don’t know how to determine what image is currently installed if the YAML specifies “latest”. ---
**Author:** ![PapaSoul](https://community.roonlabs.com/user_avatar/community.roonlabs.com/papasoul/32/99198_2.png) [@PapaSoul](https://community.roonlabs.com/u/PapaSoul)\ **Post date:** [September 15, 2026, 10:14pm UTC](https://community.roonlabs.com/t/roon-server-update-fails-on-qnap-container-stuck-at-2-71-ref-0u5dh2/324956/4 "2026-09-15T22:14:43Z")
OK it’s updating now. I manually specified the image version and it updated the image to 1.0.8 which allows the updates to be installed. Thanks for your help. ---
**Author:** ![BlackJack](https://community.roonlabs.com/user_avatar/community.roonlabs.com/blackjack/32/39743_2.png) [@BlackJack](https://community.roonlabs.com/u/BlackJack)\ **Post date:** [September 15, 2026, 10:18pm UTC](https://community.roonlabs.com/t/roon-server-update-fails-on-qnap-container-stuck-at-2-71-ref-0u5dh2/324956/5 "2026-09-15T22:18:14Z")
> [@PapaSoul](#): > > Please point me to the kb article. Why? You already pointed out other threads about the same issue. Many of those exist which got resolved. Main thread was: > [@Roon Server on NAS (Synology, QNAP, others) not updating to 2.71 build 1683 (ref#CVS9TY) \[Ticket In\]](https://community.roonlabs.com/t/roon-server-on-nas-synology-qnap-others-not-updating-to-2-71-build-1683-ref-cvs9ty-ticket-in/323518): > > I run in Docker. I installed the hotfix that was just released and restarted the container. The container is still showing up as “unhealthy” in the management tools I use. > [@PapaSoul](#): > > Is there a different method? 1. Go to the `Images` tab in `Container Station` and use the `Pull` action on the Roon Server image. 2. After that, go and recreate the app to make use of the new image. 3. Then go back to `Images` and delete the old and now obsolete image. > [@PapaSoul](#): > > I manually specified the image version and it updated the image to 1.0.8 which allows the updates to be installed. That works too but pins the version to the specified one. A simple pull in the `Image` tab will now no longer update to the current `:latest` image. ---
**Author:** ![PapaSoul](https://community.roonlabs.com/user_avatar/community.roonlabs.com/papasoul/32/99198_2.png) [@PapaSoul](https://community.roonlabs.com/u/PapaSoul)\ **Post date:** [September 15, 2026, 10:33pm UTC](https://community.roonlabs.com/t/roon-server-update-fails-on-qnap-container-stuck-at-2-71-ref-0u5dh2/324956/6 "2026-09-15T22:33:01Z")
> You already pointed out other threads about the same issue. And here we have the problem with forum based support. How am I supposed to know what the “main thread” is? There’s a bunch of threads about Docker not updating and you’re tasking me to read through 86 replies just on that single thread to glean the relevant steps to resolve the problem? This whole process should be a suggested kb article when I submit the ticket and then you personally wouldn’t need to reply to so many questions. The over-reliance on forum support is the worst aspect of this $800 software. But seriously, thanks for the quick reply and help. ---
**Author:** ![vadim](https://community.roonlabs.com/user_avatar/community.roonlabs.com/vadim/32/335515_2.png) [@vadim](https://community.roonlabs.com/u/vadim)\ **Post date:** [September 16, 2026, 11:26am UTC](https://community.roonlabs.com/t/roon-server-update-fails-on-qnap-container-stuck-at-2-71-ref-0u5dh2/324956/7 "2026-09-16T11:26:24Z")
Hello @PapaSoul Glad you are updating, and thanks to @BlackJack for getting you there quickly. On the KB article you asked for: there is not one because this was not a procedure you missed. It was a defect in the container images before 1.0.8, in how the container handled permissions on QNAP, and it stopped Roon Server updates from being applied. It is fixed, so there is nothing to document going forward. One thing worth knowing for next time, since it is what kept you on the old image while doing everything right. `image: Package roonserver · GitHub` does not make Container Station fetch anything. Recreate reuses the copy of `latest` already cached on the NAS. To move to a newer image, go to the **Images** tab, **Pull** , then recreate the application, then delete the old image. Pinning to `1.0.8` works but holds you there, so putting `:latest` back and pulling when you want to update keeps you current. On the process point: the forum is our support channel, and it is where we work. @BlackJack is not Roon staff. He is a community member who answers because he chooses to, and he had you sorted within an hour of you posting. Your frustration with the process is understandable, and it belongs with us rather than with him. ---
**Author:** ![connor](https://community.roonlabs.com/user_avatar/community.roonlabs.com/connor/32/172788_2.png) [@connor](https://community.roonlabs.com/u/connor)\ **Post date:** [September 22, 2026, 12:54pm UTC](https://community.roonlabs.com/t/roon-server-update-fails-on-qnap-container-stuck-at-2-71-ref-0u5dh2/324956/9 "2026-09-22T12:54:00Z")