Ok done and seems to work… which image should I delete now exactly?
The <none> one that is Unused and older.
Thanks, works now!
Hello Thanks a lot for your support. It works fine.
Did i miss anything as when i was looking ot the tutorial, i did not find this part “git pull & recreate” ?
by tutorial you mean Roon 's official KBs about running Roon Server in Docker? Those KBs don’t include details on how to update the container when a new container image is released.
Yes I mean this tutorial : official KB.
Thanks for your support.
Another question : how to be aware about such updates (ex : from 1.0.6 to 1.0.8)
i regularly check the GITHUB repository, to see if there is a new release / tag (currently 10 tags / versions).
@Stephen - suggestion : please announce future container image updates in the SW release notes channel.
Thanks @yo3fxy i will check the Github releases.
Sorry about that. I completely spaced that and honestly it hadn’t even crossed my mind. I’ll do better!
@ivan Maybe we should still post in the software channel that we released a newer version of the docker image?
Yes could be great as the Roon updates cannot happen if the docker is not updated. Could be also great great to add the process to update the docker image as it is not documented
I don’t think this is true. I haven’t updated my Podman container for a year or two. So long as the container has the required dependencies it will continue to run indefinately.
Roon software updates are independent of the container.
@mjw @Patatorz correct, Roon should update regardless of the docker image. It should work through the “normal” update process inside of Roon Client.
Having said that, the recent update to the docker image was to work around an issue specific QNAP and their kernel. (Release notes: Release v1.0.8 · RoonLabs/roon-docker · GitHub)
Does that help?
Not True ? It was a fact. The previous update was finalized only after the docker image update. Seems i was not the only one reading the person who initiated the thread. Anyway no need to argue as it has worked for me.
@Stephen yes it helps. Thanks
But it’s not generally true and that’s probably what @mjw meant. This was a (hopefully one-time) bug specific to QNAP and their outdated software.
I really hope it is a one time issue with QNAP. I had to build a workaround for this stuff, but unless they change how they do things I’m just waiting for the next “issue” to pop up. Honestly, I haven’t been happy with how they have maintained their stuff. I actually thought their web app and eco system was mostly dead before I even worked for Roon. I just didn’t want to spend the money to get a different NAS setup 