Justin

It's not really all that "heavy" as it doesnt actually do anything other than the function invocation to send it to both listeners. But basically ETW just drops it if...

@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 here...

Thanks for adding!

Lolz its march and I have now seen this. Still need help?

Its just because the client is built into some generic containerd calls and so rather than forking all of those go files we just have it return unsupported for windows

@TBBle / @kevpar - PTAL

Your best bet is to look at what `docker cp` actually calls and implement that. This API is just the REST API and not the rest of the `docker cli`...

Unfortunately the version of the Docker API this library supports ATM didn't have this option. It will require a version update but I will add this as a feature request...

What version of Docker.DotNet are you using? Our respond handler seems to handle this case on error by reading the body and assigning this to the `DockerApiException` message.

https://github.com/docker/swarmkit/blob/ef128ab4f5d50ffe4851d937b2b296e55562d10f/api/control.proto#L393 looks like this is now supposed to be an array but we are treating it as a single string value in the dictionary https://github.com/dotnet/Docker.DotNet/blob/b13f78e6d037e474d63e89e1fc25ddf1220c85a8/src/Docker.DotNet/Models/ServiceFilter.cs#L7