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
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 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.
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.
In #1066, we discussed adding platform information into the artifact manifest. Now we have implemented the
--artifact-platform
flag fororas push
, we should also consider if it's helpful to add the same functionality tooras 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
The text was updated successfully, but these errors were encountered: