Container image tags are not immutable
We ran into build problems in our CI/CD pipeline this morning, which appear to be caused by the removal of the specific hugo_extended container image from the registry.
It looks as if the image that had been built and made available under the 0.111.3
tag has been switched back to Alpine and that the tag is now pointing to a different image.
Specifically, we had specified the following (Debian based, amd64) image:
image: registry.gitlab.com/pages/hugo/hugo_extended@sha256:7b4d8efc4aff389c1e446c71e3aad3462f64139ffd372f4c952cb9e425f0a8e1
which had previously been tagged with 0.111.3
. Apparently, the 0.111.3
tag now refers to the following (Alpine based) image:
image: registry.gitlab.com/pages/hugo/hugo_extended@sha256:b7562f9eb4ea9cb025548278bec52dec3bf44f19330893625a1813dd746328c6
There would have been no impact of this breaking (!) change, if the original image had not also been removed from the container registry.
It would be much appreciated if the following could be ensured:
- Container image tags are immutable
- Tagged images are not removed from the registry (or, if necessary, undergo a deprecation procedure)
It might also be a good idea to differentiate between the packaged Hugo version and the container image version. A simple way would be to incorporate CalDev versioning or another unique identifier (e.g. a suitable variable from https://docs.gitlab.com/ee/ci/variables/predefined_variables.html) into the container image tag:
0.111.3-20230321.0
Thank you!