-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does "subjects" and "materials" field support multi-arch images? #105
Comments
Assuming you mean multi-arch container images (OCI/Docker), one approach would be to only list the digest of the (multi-arch) image index. I don't have enough experience to know whether that is an issue when you go to use such an image. For example, does a Kubernetes admission controller see the digest of the (multi-arch) index or the (single-arch) manifest? If the former, you should be fine. If the latter, then that may be difficult to match the hash observed with the hash in the attestation. An alternative would be to list the (multi-arch) index and all of the (single-arch) manifests, each as a separate entry in @mlieberman85 do you have experience with this? |
Yes, I believe we have just done separate values in the |
I see! Thanks for the reference! Let me know if that's a common practice - in the case that people separate them into individual items in |
hello @ywluogg ! We wanted to ping this issue and ask if it has been resolved? |
Yes this is resolved. Thanks |
Hi team, I wonder if there is a way that "subjects" and "materials" field in the statement supports multi-arch images? I know that you can specify multiple digests for different algorithms for a single image, but are there examples what a multi-arch image look like in these fields?
The text was updated successfully, but these errors were encountered: