Brandon Mitchell

> > I have a high level concern that we're trying to document the mixture of runnable Images and Artifacts in the same Index. Is that something we want to...

Given the various scenarios we're seeing, and knowing there will be more scenarios in the future, perhaps instead of being prescriptive in exactly what fields are defined and we should...

> Why would we prohibit container runtimes, and their fat clients, from executing/processing artifacts? My phrasing is that container runtimes trying to execute/process it makes it a container image. It's...

> Let's not leave out the index may or may not include platform filters, and "implementations SHOULD support" "application/vnd.oci.image.index.v1+json (nested index)" and "an encountered mediaType that is unknown to the...

This gets a decline from me as well unless there's a response to https://github.com/opencontainers/image-spec/issues/1073#issuecomment-1589550392 showing why it's needed.

[Docker has a syntax](https://docs.docker.com/engine/reference/commandline/build/#git-repositories) where they use `#` and `:` to separate the git repo name from the path and tag/ref. I'm not sure how I feel about that for...

For that problem, the directory may not be enough. From the same directory, multiple images may be generated. E.g. different build tools, docker can point to different Dockerfiles, build args...

Since this is indirect, we should push upstream to update their dependencies: ``` $ go mod why gopkg.in/yaml.v3 # gopkg.in/yaml.v3 github.com/opencontainers/image-spec/schema github.com/xeipuuv/gojsonschema github.com/xeipuuv/gojsonschema.test github.com/stretchr/testify/assert gopkg.in/yaml.v3 ``` It doesn't look like...

Does this mean `/` would be chowned to the user, with 755 permissions? Are there implementations that do this already?

When I first saw this, I was thinking of the `COPY --link` feature in buildkit, where you don't necessarily know the parent folder state, but inferring it is probably a...