What is the version of your ORAS CLI
v1.1.0
What would you like to be added?
We have seen multiple ORAS users who wanted to pull OCI artifact or container images from a remote registry to a local OCI archive or an OCI layout. oras copy has options to pull the subject/referrer from remote registry to OCI layout (or from OCI layout to registry).
However, Pull is commonly understood but Copy is an extra cognitive step for most of the new ORAS users. We need to design and provide an intuitive way to enable users pull an OCI artifact/image from registry to a local OCI archive or an OCI layout.
Why is this needed for ORAS?
In order to provide a natural experience of pulling content from registry to local and make the design principle conforms to users’ default habits.
We received several ORAS user requests on this feature. Related discussion: https://cloud-native.slack.com/archives/CJ1KHJM5Z/p1697701836678159?thread_ts=1697645768.389369&cid=CJ1KHJM5Z
Are you willing to submit PRs to contribute to this feature?
What is the version of your ORAS CLI
v1.1.0
What would you like to be added?
We have seen multiple ORAS users who wanted to pull OCI artifact or container images from a remote registry to a local OCI archive or an OCI layout.
oras copyhas options to pull the subject/referrer from remote registry to OCI layout (or from OCI layout to registry).However, Pull is commonly understood but Copy is an extra cognitive step for most of the new ORAS users. We need to design and provide an intuitive way to enable users pull an OCI artifact/image from registry to a local OCI archive or an OCI layout.
Why is this needed for ORAS?
In order to provide a natural experience of pulling content from registry to local and make the design principle conforms to users’ default habits.
We received several ORAS user requests on this feature. Related discussion: https://cloud-native.slack.com/archives/CJ1KHJM5Z/p1697701836678159?thread_ts=1697645768.389369&cid=CJ1KHJM5Z
Are you willing to submit PRs to contribute to this feature?