Skip to content
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

Closed
ywluogg opened this issue Aug 9, 2022 · 5 comments
Closed

Does "subjects" and "materials" field support multi-arch images? #105

ywluogg opened this issue Aug 9, 2022 · 5 comments

Comments

@ywluogg
Copy link

ywluogg commented Aug 9, 2022

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?

@MarkLodato
Copy link
Contributor

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 subjects. You can just give each a unique name.

@mlieberman85 do you have experience with this?

@mlieberman85
Copy link

Yes, I believe we have just done separate values in the subjects

@ywluogg
Copy link
Author

ywluogg commented Aug 9, 2022

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 subjects, using the qualifier for adding additional identifiers could be one of the choices.

@marcelamelara
Copy link
Contributor

hello @ywluogg ! We wanted to ping this issue and ask if it has been resolved?

@ywluogg
Copy link
Author

ywluogg commented Jan 8, 2024

Yes this is resolved. Thanks

@ywluogg ywluogg closed this as completed Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants