Add support for "latest" container tag #3
Labels
Comments
sampaccoud
added a commit
that referenced
this issue
Apr 26, 2018
A small refactor was necessary to be able to keep a "latest" version of our images on DockerHub. I kept the idea of building the image with its tag and found a way to retrieve the tag as an output of the build method in order to be able to tag and push the same image with the "latest" tag. Fixes #3
sampaccoud
added a commit
that referenced
this issue
Apr 26, 2018
A small refactor was necessary to be able to keep a "latest" version of our images on DockerHub. I kept the idea of building the image with its tag and found a way to retrieve the tag as an output of the build method in order to be able to tag and push the same image with the "latest" tag. Fixes #3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Purpose
Published images are tagged with a version corresponding to the original image version, but we do not publish a
latestrelease. Even if we strongly forbid to use a latest release in production (we should explicitly use a pinned release), it could be useful for some users to pullfundocker/openshift-nginxfor testing purpose.Proposal
latesttag during the build procedureThe text was updated successfully, but these errors were encountered: