Kevin Parsons

Just to chime in here with my use case, I'm currently trying to debug some weird CI failures that I think are due to bad data being cached. Currently I'm...

> The pull request [opencontainers/image-spec#829](https://github.com/opencontainers/image-spec/pull/829) dealing with the specification as proposed above > > > The easiest fix here is probably to get ArgsEscaped added officially on the OCI image...

> Any update on this by chance? Note that its not just _Shell_ form its also _Exec_ form that is broken. And the fix proposed will only fix _Shell_ form...

> Hey! :) > > This sounds good, do you want to do `ArgsEscaped` as a "hack" patch to the image config in this repo or do you want to...

> CMD ["powershell.exe", "c:\\test\\test.ps1"] I would expect this form to work. Is it possible you have another `CMD` or `ENTRYPOINT` elsewhere in your Dockerfile or base image which still uses...

I didn't notice this PR already existed, but I just opened #974 which addresses the old Windows version issue by detecting when EnableVirtualTerminalProcessing fails, and falling back to no colors...

We encountered this with our containerd shim on Windows, where we use a single shim for every container in a pod. It was hit when publishing multiple events back to...

@crosbymichael can you clarify what this is tracking? As far as I know, we already use TTRPC with named pipes on Windows. :)

> All that said, the matcher is needed by the "pull" operation, which is really "Network to content store", the snapshotter doesn't actually see the Matcher at all. So per...

> @kevpar - I thought that is why we added annotations to PullImage for CRI so we passed in the sandbox so we knew what type of thing to do...