Bug: renovate is unable to track image updates (unsupported/unversioned value) #285
Description
Renovate is unable to track image updates. The startup-script image uses sha256 digests that seem unsupported. Versioning needs to be amended for renovate to take care of automatic updates.
Details
- Mar 26th: Image update scripts were replaced by renovate
- Note the intention to switch to pinned digests
- Note tracking package names (line 102 of
renovate.json5)
- Mar 26th: Alpine image needed manual update
- June 26th: Alpine image needed manual update
- nodeinit image also needed manual update in
cilium/ciliumrepo
When running LOG_LEVEL=debug renovate --platform=local on a local copy of the repository,
DEBUG: Dependency quay.io/cilium/image-compilers has unsupported/unversioned value 5569a29cea6b3ad50aeb03102aaf3dc03841197c (versioning=docker) (repository=local)
DEBUG: Dependency quay.io/cilium/image-tester has unsupported/unversioned value dd09c8d3ef349a909fbcdc99279516baef153f22 (versioning=docker) (repository=local)
DEBUG: Dependency quay.io/cilium/image-tester has unsupported/unversioned value dd09c8d3ef349a909fbcdc99279516baef153f22 (versioning=docker) (repository=local)
DEBUG: Dependency quay.io/cilium/image-compilers has unsupported/unversioned value 5569a29cea6b3ad50aeb03102aaf3dc03841197c (versioning=docker) (repository=local)
DEBUG: Dependency quay.io/cilium/image-tester has unsupported/unversioned value dd09c8d3ef349a909fbcdc99279516baef153f22 (versioning=docker) (repository=local)
DEBUG: Dependency gcr.io/go-containerregistry/crane has unsupported/unversioned value latest (versioning=docker) (repository=local)
Note: the repetition of debug messages is because multiple Dockerfiles contain the same images (e.g. images bpftool, compilers and llvm).
According to the docker versioning documentation for renovate,
Are commit hashes supported?
No, Renovate ignores Docker image tags that look like a Git commit hash.
References
Metadata
Metadata
Assignees
Labels
No labels