Brandon Mitchell

Depending on the exact workflow, I think there are a few other options. 1. You can call the `regclient.ManifestGet` and `regclient.BlobGet` commands directly, and either store in your own content...

> I'm trying to use this ([here](https://github.com/quay/claircore/compare/main...hdonnay:claircore:hack/test-fixtures), if interested) to keep fixtures for various kinds of integration tests in referrers of a single tag. That helps a lot. I think...

> I'll give that a spin; the cursory reading I gave it made me think that it would not work correctly with an absolute path. `ocidir://` defines the scheme, and...

@rchincha > This is likely going to a fully vertical integrated stack (HTTP APIs, layout, interaction with zot-specific extensions) etc - so basically a parallel implementation of "docker distribution"-lite. This...

We discussed this during the OCI meeting at KubeCon today and decided it makes more sense to add this to image-spec instead of a separate repo. I'm closing this and...

Reopening to continue the discussion from the mailing list: https://groups.google.com/a/opencontainers.org/g/dev/c/PpzsQMOnda4 cc @vbatts @Jamstah @sajayantony

> There's not a lot in the minutes explaining the decision to include it in image-spec, can anyone remember the reasoning? I believe @imjasonh weighed in on that. The impression...

None here. I haven't seen any PRs that implement this while also differentiating between an expected exit, an unexpected exit, and a container that hasn't started yet.

@pschichtel see my comment above https://github.com/sudo-bmitch/docker-stack-wait/issues/19#issuecomment-1309058348

Closing this one because of #999.