Updating Roon on QNAP NAS after Docker Install

Roon Software Discussion QNAP/Synology NAS
1

I managed to make the changes to install roon on docker a while ago, but now have a message when I start roon that there is an upgrade for my server - version 2.70 (Build 1671). I clicked to upgrade and the installation fails at 55% with eh message:

Status : Stopped
Version : 2.65 (build 1653) production
QPKG-Version : 2023-03-07
ffmpeg : user supplied version. along with an option to change my database location.

I am totally confused now. Roon still works fine but why is an older version not installing? Is the roon app on QNAP not now needed during to docker installation? should I just delete the roon app and ignore future upgrades for the server or do I have a problem?

Please can somebody help? I will be very grateful for any advice.

Thanks

2

The QPKG is no longer supported; you need to install the new container using Docker Station.

Please refer to the Help Center, and configuration generator.

3

Ok thank you

4

should I delete the roon app on QNAP then?

5

No, not until you have Roon running with Docker, and a backup restored. Only then should it be removed.

7

Ok thanks I already have it running with Docker, my problem was updating the roon version. Now I see it must be done via docker, thank you. So I’ll delete the app.

8

If you have Roon running in Docker, ththen updating is done via the app. You do not have to update the container.

Therefore, stop the original Roon on NAS instance to be certain that you are using the container instance, and update using Settings → About.

Once you are up-to-date aante certain your backup was restored, you can delete the old instance.

9

Hi mjw,

Do you know why my docker install won’t update?

IMG_2113
IMG_21131284×773 72.9 KB

The update progress bar shows automatically and after “installing” it shows this error message. 1683 should be available. NAS and all apps are updated as well.

The server runs flawlessly, I noticed this accidentally. There’s no need for an immediate update.

Thnx

10

check the roon-container logs for lines like the ones below & make sure you are running version 1.0.8.

roonserver | Roon Docker image 1.0.8 starting.
roonserver | Detected a kernel where fchmodat2 (syscall 452) returns EFAULT.
roonserver | That breaks tar when restoring modes (dirs, files, symlinks) and is a
roonserver | known QNAP kernel issue. Enabling a compatibility shim for tar only.
roonserver | Shim verified: probe extract now succeeds.
roonserver | Detected existing RoonServer install (branch: production).
roonserver | Resolved ROON_INSTALL_BRANCH=‘production’.
roonserver | Installed branch ‘production’ matches requested branch; no reinstall needed.
roonserver | Image: 1.0.8
roonserver | Branch: production
roonserver | Roon: 2.71 (build 1683) production

11

Please make sure you run the latest image (v1.0.8).

12

ah ok great thank you

13

This is turning into a long and frustrating day…

when I try to import the 1.0.8 I get the following message:

Screenshot 2026-09-01 at 15.51.42
Screenshot 2026-09-01 at 15.51.421274×742 149 KB

any ideas pls?

14

Can’t you open the console and simply use Docker Run from the configurator?

The error means that Container Station doesn’t know what to do with the tar archive.

15

The Image is not equal to a container file. I usually go to the Images tab and pull the image in question. If a newer version is available this will download it. Then go to Applications tab and recreate the app in question (to use the new image if there is one). See also:

https://www.qnap.com/en/how-to/tutorial/article/container-station-quick-start-guide

16

go to Container Station → Images , click on config-wheel and select pull

Screenshot 2026-09-01 at 17.07.58
Screenshot 2026-09-01 at 17.07.581546×496 33.3 KB

followed by going back to Applications & selecting recreate

Screenshot 2026-09-01 at 17.11.16
Screenshot 2026-09-01 at 17.11.161556×876 53.8 KB

optional but recommended, go back to the Images section and delete the old image version (identified by the the hash in the ID column)

17

I’m indeed on 1.0.6. Will update later. Thnx so far.

18

Brilliant thank you!

For some reason I couldn’t see the second 1.0.8 image despite several attempts to pull it. evenyually I closed Container Station and re-opened it - and there it Was! I am very grateful to all for your help. I will screen grab so I don’t forget when updating in future.

19

Hi, does this procedure require restoring backup and setting up new folders etc.?

20

No it does not.

21

Thank you very much. Updated and running flawlessly.