Does anyone know how long after a new version drops that it shows up on Roon’s GitHub as a docker container? See: Package roonserver · GitHub
Trying to determine if I should update in app or wait for the container to be released.
Thanks.
You don’t need to update the container. We only update the container when there is an issue with the container itself.
The server is updated through the client and is independent of the container version.
Let me know if you have any questions.
Thank you! Greatly appreciate the helpful response. So, the container when first installed has the server and its dependencies. Following this, updating the server within the client is the recommended approach. I’m guessing this means if there is a dependency requirement change, the container is updated at that time? And the container being updated on your GitHub site each month is effectively the same container with new roonserver version for people installing the docker container the first time? This is helpful context. I had enabled watchtower on a 24 hour cycle to catch any container updates and was wondering why a new container hadn’t been pushed yet. Many thanks.
The container actually pulls the server on first run. So, if you needed to install the container from scratch on a new device it’ll pull whatever the currently released (or EA release) is available at that time.
We originally approached it from the idea of release a new container each time there was a new version of Roon Server but decided against that. So, essentially, we are using the docker image as an abstraction layer between the “hardware” and our software. The driving force behind this was that QNAP hasn’t updated their glibc library in over a decade 
If we end up in a position where we need to update the dependencies on the container or need to fix a bug with the container setup we’ll release a new version of the container. The recent churn you saw was because it was the first time we were supporting containers.
Sorry, yes, the current plan is to always release to the current github container repo 
Such helpful context. Yes, the churn seemed timed with the monthly roonserver updates which is what tricked me. Thanks so much! Out of curiosity, I assume you recently made the docker container officially supported and stated it was now your recommended install approach to create consistency in support across Linux distros? If I’m correct, is it working? Noticed a big spike on downloads.
It was largely a rapid response around our now net10.0 based server and it not working on older hardware due to older versions of glibc.
I’m not sure we have come out and said it is “officially” the preferred way to run it on Linux. If you are running QNAP and older Synology devices it is now the only way to possible run it.
Having said that it makes things much simpler and nicer in some respects. I’ve liked using for testing and other things. It has allowed me to build up some stuff around it so that I can better track stats/data/logs/etc.
I was referring to this: RoonServer Docker image is live!
The official RoonServer Docker image is now available, and Docker is now our recommended and supported deployment path for self-managed server environments.
I like all the tracking you have built.
I guess that is fairly official 
I forgot about that.