Billy Zha

> > Before upload any blob to a registry, the digest must be specified. > > Unless you can get the digest before archiving is done, Otherwise it's not possible...

Yes, the digest calculation can be done while packing and this optimization has already been applied in oras-go. The question is after getting the digest, oras CLI still need to...

@ProbstDJakob Besides from the seek operation, what you described is already implemented in [here](https://github.com/oras-project/oras-go/blob/15ee0be60ddc4a54b285044ad693fd35a9899549/content/file/file.go#L508-L541). P.S. I think this discussion has gone too far from this issue and I have created...

ORAS CLI still have deps on github.com/docker/docker-credential-helpers v0.7.0. Resolving this issue is depending on https://github.com/oras-project/oras-credentials-go/issues/67 and merging of https://github.com/oras-project/oras-credentials-go/pull/68

Closing as it's covered via `oras push/attach --oci-layout` in main branch. @griffin You may use a local folder `test` to stage the manfiest before pushing it to a remote registry....

Closing this as the json output now is an [OCI index](https://github.com/opencontainers/image-spec/blob/v1.0/image-index.md#oci-image-index-specification) and contains referrer digest.

> What is in that HTTP request? Can you link to the relevant parts of the code? Thanks for reminding. This is talking about the implementation of seekable reader utility...

@mathieu-benoit Thanks for sharing. You can actually pipeline commands into one line like below: ``` IMAGE="myimage" oras manifest fetch $IMAGE |jq '.annotations.foo = "bar"' |oras manifest push $IMAGE - ```...

moving to future milestone as there is no user requesting docker config support for customer header

@ziggythehamster Regarding pulling without tag or digest, can you kindly share a real case, like what's in the `blobs` folder and what's the content of `manifest.json`, and how you expect...