[Docker] Clarify tags latest (0.8.0) not being "latest" v0.8.1?
Closed this issue · 3 comments
Describe the bug
Pulling the docker image quickwit/quickwit gives v0.8.0 which is not the latest tag v0.8.1
Example:
docker run --rm quickwit/quickwit:latest --version
Quickwit 0.8.0 (x86_64-unknown-linux-gnu 2024-04-23T08:28:44Z 6fd8dc8)
While:
docker run --rm quickwit/quickwit:0.8.1 --version
Quickwit 0.8.1 (x86_64-unknown-linux-gnu 2024-03-29T14:09:41Z e6c5396)
The build date for v0.8.1 is before v0.8.0 tho 🤔
Expected behavior
Having a clear and semantic versioning of the docker images would help docker deployments :)
In our case, latest is actually not the latest release but the latest image we published, which can be anything since we publish a new image after a PR is merged on main or when we produce a custom image for testing.
I'll see if we can easily modify our CI workflow to publish a latest tag exclusively when we release a new version of Quickwit. In the meantime, I suggest you move away from using that tag, which is considered bad practice:
Thank you @guilload I got your inputs.
What is also confusing is that from the documentation it mention to use docker run --rm quickwit/quickwit --version:
which:
$ docker run --rm quickwit/quickwit --version
Quickwit 0.8.0 (x86_64-unknown-linux-gnu 2024-04-23T08:28:44Z 6fd8dc8)
Again pulls the :latest tag same as 0.8.0
I've just fixed the CI workflow and republished the latest tag to point to the 0.8.1 release.