You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 3, 2025. It is now read-only.
This SHOULD be a fully qualified reference name, without any assumed default registry. (e.g., registry.example.com/my-org/my-image:tag instead of my-org/my-image:tag).
This SHOULD be the immediate image sharing zero-indexed layers with the image, such as from a Dockerfile FROM statement.
This SHOULD NOT reference any other images used to generate the contents of the image (e.g., multi-stage Dockerfile builds).
If the image.base.name annotation is specified, the image.base.digest annotation SHOULD be the digest of the manifest referenced by the image.ref.name annotation.
I'd like to discuss and propose that kaniko set these annotations on images it produces by default, pointing to the ref and digest of the FROM image that produces the final built image. (note: this does not include any images implicated in multi-stage builds)
The OCI spec recently added specification for two new standard annotations, to facilitate pointing to a base image:
More details and further motivation here: https://articles.imjasonh.com/oci-base-image-annotations
I'd like to discuss and propose that kaniko set these annotations on images it produces by default, pointing to the ref and digest of the
FROMimage that produces the final built image. (note: this does not include any images implicated in multi-stage builds)