Sebastiaan van Stijn

Thanks! Right, so from that information, it seems indeed that some state / metadata should be preserved somewhere. I must admit I'm not familiar enough with options where to store...

Hm, not sure about an issue discussing health checks, but I can see this being application-specific, so not part of the specs for that reason. Possibly @stevvooe knows more about...

@jonjohnsonjr @vbatts @mikebrow @dmcgowan @SteveLasker ptal (not sure if this is the right location for this discussion, or if it should be discussed in the OCI call; I just noticed...

I must admit I'm not the most proficient reader of specifications, but good to hear I'm not the only person that was a bit confused by it 😅 (which may...

> If we suddenly change the standard to not allow unknown blob types in images and allow tools to reject them, use cases like this will no longer be possible....

> No; the distribution spec is for repos serving content over http. skopeo translates to/from OCI images according to the OCI images spec. Yeah, poor choice of words; was trying...

I see I forgot to reply to some of the comments > Regarding the ambiguity of the MUST clause. The intention of that sentence is to say that implementations should...

The problem is that currently the correct behavior is effectively "undefined". See my earlier comment about layers using mixed compression (which IMO should be a valid use case). Without any...

Unfortunately, it doesn't, because for runtimes that support both `zstd` and `gzip`, selection is now ambiguous. Take the following example; ```json { "layers": [ { "mediaType": "application/vnd.oci.image.layer.v1.tar+gzip", "size": 12345, "digest":...

> The final filesystem layout MUST match the result of applying the layers to an empty directory "Applying the layers" is very ambiguous combined with the other requirements (more below:)...