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
As we (@developer-guy) discussed a similar thing at containerd/nerdctl#577, @.AkihiroSuda proposed an idea to verify Dockerfile FROM images in nerdctl build and nerdctl compose up --build. We can traverse the entire base images since cosign already have a support for verifying signatures on the base images that specified in the Dockerfile.
# only verify the base image (the last FROM image)
$ cosign dockerfile verify --base-image-only <path/to/Dockerfile>
From nerdctl build (and docker buildx) perspective, modifying BuildKit is probably not necessary if we can have cosign dockerfile resolve command proposed in sigstore/cosign#707sigstore/cosign#648 .
nerdctl build (and docker buildx build) could exec cosign dockerfile resolve to convert the Dockerfile before calling BuildKit.
As we (@developer-guy) discussed a similar thing at containerd/nerdctl#577, @.AkihiroSuda proposed an idea to verify Dockerfile FROM images in
nerdctl build
andnerdctl compose up --build
. We can traverse the entire base images since cosign already have a support for verifying signatures on the base images that specified in the Dockerfile.Additional Context
cosign verify-dockerfile
is dangerous sigstore/cosign#648The text was updated successfully, but these errors were encountered: