Versions in docker (stable, mainline, nightly) and differences to github-versions itself #25903
-
|
Hi, Im using coder with docker-containers: https://github.com/coder/coder/pkgs/container/coder/versions?filters%5Bversion_type%5D=tagged&page=1
Would also be better to have explizit tags like stable, mainline for docker-containers. Was also searching some kind of nightly for testing purposes, to see things of the upcoming release. But only found some kind of sha-packages I couldn't match. Would be nice to have a nightly-tagon docker. Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
hey @Cyber1000, The "latest" tag on GitHub represents the current stable version, and the "latest" tag on the container image registry represents the biggest/most recent version (mainline). We don't have a mainline or stable tag on the container registry because mainline inevitably gets promoted to stable. Here's the logic (from "Releases"):
Now, for your questions:
I agree that we should ideally have a NOTE: I would recommend against using nightly on your main deployment because it will inevitably break. |
Beta Was this translation helpful? Give feedback.
-
|
thanks for your answer! Well it's just a homelab for myself, so mainline would be fine. Thanks for the nightly tag, wasn't aware of this, would just use this as a second docker if there is some feature I want to try in advance |
Beta Was this translation helpful? Give feedback.
hey @Cyber1000,
The "latest" tag on GitHub represents the current stable version, and the "latest" tag on the container image registry represents the biggest/most recent version (mainline).
We don't have a mainline or stable tag on the container registry because mainline inevitably gets promoted to stable.
If you are running in a homelab, mainline is fine, otherwise for production you'd want to use stable, which is usually updated by hand by admins.
Here's the logic (from "Releases"):
Now, for your questions:
ghcr.io/coder/coder:latest