I'm running 9router in Docker and noticed that the version shown by the npm package appears much newer than the image I get with decolua/9router:latest. The dashboard also checks npm for updates, so it keeps showing an update notification, while the "Update now" action runs npm i -g 9router@latest, which doesn't actually update the server being run from the container. Is the Docker publishing process delayed, or does the latest tag simply not reliably point to the newest release? Should Docker users pull an explicit version tag, build their own image, or use a different update method?
2 Answers
The newest release does appear to be available on Docker Hub, including an explicit 0.5.50 tag. The confusing part is that the latest tag may lag behind the version-specific tags, so pulling decolua/9router:latest can give you an older image. Try pulling the exact version tag instead of relying on latest.
This looks more like a Docker tag problem than a missing container flag. The npm-based updater isn’t useful inside this image because the running server comes from the image’s bundled files, not the globally installed npm package. For predictable updates, pin the Docker image to a specific release tag and recreate the container when upgrading.
That explains it. The explicit version tags are ahead, while latest isn’t consistently being moved to the newest release. My container had resolved to an older digest even though a newer version tag was already available.