· I run Roonserver on a QNAP TVS-471 and yesterday I made the step to install Roonserver in a Docker in Container Station. I succeeded to get Roon up- and running again and Roon runs much smoother now, that is a step forward.
Yesterday evening (European time) there was an update available to version 2.65. Roon gave me the warning that the update was available and I immediately tried to upgrade my version of Roon to 2.65. After Roon downloads the update and tries to install it I get the message: "There was an error checking for an update". What am I doing wrong?
I tried it again this morning and I still have the same error message. The Roon app on my computer and on my phone are already updated to version 2.65, but Roonserver refuses to update to the new version.
Can somebody help me with this? Thanks in advance!
Tell us about your home network
· We have a standard modem/router from KPN and everything works fine.
Congratulations on successfully migrating to Docker!
The error you are seeing is completely normal. In a Docker environment, the Roon app doesn’t have permission to overwrite its own container image, so the standard in-app server updates will fail.
From now on, you will update the server directly through QNAP Container Station:
Open Container Station and go to the Containers tab.
Stop your Roon container.
Once stopped, click the container’s name, open the Edit drop-down menu at the top right, and select Recreate Directly.
Choose “Try pulling the image from the registry…” and click Yes.
Container Station will automatically download the latest 2.65 image and restart your Roon Server.
Are your files safe? Yes! Recreating the container only updates the Roon software itself. Because you mapped your folders using volumes during setup, your database, settings, and music are safely preserved on your NAS drives.
I am happy that I succeeded migrating to Docker, as I said Roon runs much smoother after migrating to Docker. And I am also very happy to read that the error message is completely normal in the new situation.
As soon as I get home after work I will try to download the latest 2.65 image following your instructions. I will let you know if I was able to upgrade to version 2.65. I assume this is the standard procedure I need to follow for every future update?
AFAIK gets the Roon Server program downloaded and installed on first run, after that it is the usual self-update of Roon - that doesn’t work for you. So I would rename what’s in your new Roon folder after stopping the Roon Docker Application and see if it gets recreated and the new version installed.
I did it! I managed to update to version 2.65, it was not as easy as you described, or maybe I did something wrong.
What I did after stopping de roonserver is creating a new folder on the SSD, I named it “roon 2.64”, I moved the content of my existing roon folder to the new “roon 2.64” folder.
Then I recreated the container as you described.
When I started the Roon application it didn’t connect automatically to the newly created Roonserver. But after choosing the option to connect to another server and restore a backup from last night, Roon was starting up again. And now Roon version 2.65 is running!
Maybe there is an easier way, but I managed to upgrade the Roonserver.
