Nalin Dahyabhai

Okay, I'll switch this over to doing that.

Okay, the changes are ready.

With podman@a702d442e98850f56bc86ee4d6adf5f493a06201: ```shell podman create --platform linux/arm/v6 quay.io/libpod/busybox:musl podman create --platform linux/arm/v7 quay.io/libpod/busybox:musl ``` only pulls an image once. I _think_ this is the cause of a flake we saw...

The test ([one example](https://cirrus-ci.com/task/6506882769092608?logs=main#L363)) builds with `--all-platforms`, which iterates through a map of the target platforms, building for each in turn. Depending on which order we process `linux/arm/v6` and `linux/arm/v7`,...

I don't like the idea of special casing arches that are known to have variants, because I think we're going to start seeing linux/amd64/v2 at some point, too. The crux...

This is one of those differences in behavior between the BuildKit-based version of `docker build` and the V1 version of it, where our behavior around treating VOLUME locations imitates the...

Out of band, we have an image with an OCI media type, but which is using Docker media types to describe its config blob and layers: ```json { "schemaVersion": 2,...

> being generated by https://github.com/kubevirt/containerdisks/blob/main/pkg/build/build.go with changes from https://github.com/kubevirt/containerdisks/compare/40fc44a45797c5e02bfdf72d1f161fc0bb155254..c39ddf6c0af1b76817541c0cdae8e744003b252d applied. ... or reverted, as it may be.

I expect that was built using https://github.com/kubevirt/containerdisks/pull/81, where the mediaType values being used are all hard-coded.

> It would be ~easy enough to handle _some_ of the code paths; e.g. `Inspect` can ignore the manifest media type and choose an implementation based on just the config’s...