Jon Johnson

I think it's probably safe to close this. There was some mention of a better listing API in this thread, which is captured here: https://github.com/opencontainers/distribution-spec/issues/222 We also have https://github.com/opencontainers/distribution-spec/issues/250 which...

> with respect to pushing a blob, does this mean that the registry does not make an association between a blob (layer) and an image, but rather allows the client...

> server sends back location to upload (expires in N seconds, I chose 10) I don't have any data to support my opinion, but this seems low. I could see...

> for a chunked upload session, does this mean that all PATCH and final requests should use the same original session id (the location) Clients should not be constructing the...

> I assume this is a 256 hexdigest of the body itself and the size of the body (the manifest). But how can we calculate this if it's supposed to...

> And I hope it's okay that I'm asking questions ... I would also argue that most of these details should be stated very clearly in the spec (and not...

I'd throw in `` as a reasonable term for a tag or digest.

> If we can't articulate a good use-case, then what value does it have to say a registry is OCI-Complaint if it can only do one distinct thing? I guess...

> How can you distribute something if you can't first load it? What does `load` mean? > But why can't we agree a functioning implementation of the distribution spec, at...

What I actually care about is that there is _some_ distinction for a registry that implements pull, even if it doesn't implement anything else. Especially for things like distributing base...