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

Support --artifact-platform in oras attach? #1537

Open
Wwwsylvia opened this issue Nov 21, 2024 · 2 comments
Open

Support --artifact-platform in oras attach? #1537

Wwwsylvia opened this issue Nov 21, 2024 · 2 comments
Labels
question Further information is requested
Milestone

Comments

@Wwwsylvia
Copy link
Member

Wwwsylvia commented Nov 21, 2024

In #1066, we discussed adding platform information into the artifact manifest. Now we have implemented the --artifact-platform flag for oras push, we should also consider if it's helpful to add the same functionality to oras attach.

It would be something like:

oras attach localhost:5000/oras:v1.0.1 --artifact-type "application/vnd.sbom" --artifact-platform linux/amd64 oras--1.0.1.arm64_monterey.bottle.tar.gz
@FeynmanZhou
Copy link
Member

It may require a valid scenario to justify why platform information is necessary for a referrer artifact. Suggest keeping this issue open for discussion and feedback gathering from the community.

@Horiodino
Copy link
Contributor

well consider attaching platform-specific NVIDIA GPU drivers to a container image( Ai era, everyone and their neighbor is running kubernetes GPU clusters). Without platform info in the referrer artifact, tools must download and inspect all driver variants to find a compatible one. By adding --artifact-platform to oras attach, tools can immediately identify and fetch only the platform-appropriate driver
suppose if we not , then download all driver artifacts ,examine their contents to determine compatibility ,select the appropriate one for the target platform and so on.

what you folks think?

@Wwwsylvia Wwwsylvia added the question Further information is requested label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants