Derek McGowan
Derek McGowan
A few things here to consider: (1) Its clear registry's scope does not match the scope that containerd is guessing it will be from the reference. It might be a...
I'm going to close this one out. If any of the remaining items still apply, they can be opened up separately.
This project is open source, feel free to add reviews. Especially if you have a fork and verified the change, thats valuable for determining the change is good. This project...
> The direction depends on the perspective. The images and registry is designed around a merkle tree. The reference artifact ends being the top hash in the merkle tree (even...
The core issue is related to consistency. (1) Has the full list been uploaded to the registry? And (2) Are all the dependencies correct and available? I believe the deviations...
My attempt here is to find some common ground that allows registries and clients to preserve their data models while supporting the widest range of use cases. I also don’t...
I should probably put up my draft soon to discuss more specifics. My thought is the registry could make that determination per repository and the client would know the correct...
``` // Register a type with a base URL for JSON marshaling. ``` We should probably prefer JSON if the type is manually registered, otherwise proto can already be preferred...
#10177 may have addressed this
The only problem with unconditionally calling `Prepare` is that the already exists error is relying on the `containerd.io/snapshot.ref` label, which snapshotters look at to produce the already exists error. We...