Why are docker images so late vs the releases?

[wsw70]

I checked my docker-powered blinko and I see the following info:

Server: v1.4.3
New client version available: v1.5.5

My docker image is set to blinkospace/blinko but pulling a new one does not update it (it is up to date with the published image). I am not sure what the server vs client version is because there is no "client" per se - the web page is served from the server.

[dosubot[bot]]

Docker images for blinko often lag behind releases because the image build and publish process can be delayed or encounter issues—sometimes the image is tagged but doesn't actually contain the latest app version, or the build fails and isn't pushed promptly. This has been reported by other users as well, where the Docker image tag and the version shown in the app don't match, or the image is one version behind the release notes (example, another).

In blinko, the "server" version is the backend API/service, and the "client" version is the frontend code (the web UI) served to your browser. Even though both are delivered by the server in Docker, they can be versioned separately—so you might see a new client version available even if your server (Docker) is up to date with its own image (source).

If pulling the latest Docker image doesn't update your version, it's likely because the image on Docker Hub hasn't been rebuilt or published for the latest release yet, or there was a problem in the build pipeline. This is a known workflow issue and not something you can fix from your side—it's up to the maintainers to ensure the Docker images are built and pushed in sync with releases.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[wsw70]

1.4.3 docker image was published yesterday. So the docker image publication is not stuck. How to update the "client" part then?

[dosubot[bot]]

The "client" in blinko is the frontend web UI, which is built and bundled into the Docker image at build time. When you pull a new Docker image, both the backend (server) and frontend (client) should update together. If you still see an old client version after updating the image, it's almost always due to your browser caching the old frontend files. Try clearing your browser cache or doing a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) to force the browser to load the latest client assets from the server. This is a common step recommended for UI issues after Docker updates (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[wsw70]

This is not this, please stop providing generic answers not related to blinko itself (I am arguing with a bot... 🤡)