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
I had a build that had two FROM lines, one was registry.access.redhat.com/ubi9/ubi:latest and the other was registry.access.redhat.com/ubi9:latest.
The build failed later on when trying to inject the base image references into the SBOM because the /shared/base_image_digests file had an invalid format.
I think the culprit is the buildah images --format '{{ .Name }}:{{ .Tag }}@{{ .Digest }}' --filter reference="$image" invocation, which (I think) limits the list of images returned to only ones that match the string $image as a filter. That would at least make sense why this shows up as an error when one base/builder image is a substring of another.
I had a build that had two FROM lines, one was
registry.access.redhat.com/ubi9/ubi:latest
and the other wasregistry.access.redhat.com/ubi9:latest
.The build failed later on when trying to inject the base image references into the SBOM because the /shared/base_image_digests file had an invalid format.
I think the culprit is the
buildah images --format '{{ .Name }}:{{ .Tag }}@{{ .Digest }}' --filter reference="$image"
invocation, which (I think) limits the list of images returned to only ones that match the string$image
as a filter. That would at least make sense why this shows up as an error when one base/builder image is a substring of another.Related: #1790
The text was updated successfully, but these errors were encountered: