· 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.
> 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”.
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.
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.
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.