Michal Augustýn

It would be still great to have support for gRPC-Web in grpcurl. I'm using grpcurl to quickly test/check a gRPC services so it would be absolutely great if I could...

I tried to export the image to a tar file (using `docker save`) and the `manifest.json` is this: ```json [ { "Config": "68204dc2fc12499d321ef43f00c439bbf2300b280d14737a92841d4b22ddd58c.json", "RepoTags": [ "openjdk:11.0.1-windowsservercore-ltsc2016" ], "Layers": [ "37c83953227860836879b642445fc27e45d6fe2bd1769735aaec5c8f6e433a83/layer.tar",...

So I guess that support for these fields in the parser could move us further.

I'm also unable to find any official documentation, just source code :) I'm not sure if a design doc is necessary - it's up to you. For me, it seems...

My experience is that Docker downloads these foreign layers - it needs them to start a container based on that image. If you try to push the pulled image, then...

> Then we could have a Jib config option to allow pushing foreign layers. Exactly! It would be great to read the default value of this option from the `daemon.json`,...

Yes, to make it working, ignoring `LayerSources` could move us further. But please note the comment for the `application/vnd.docker.image.rootfs.foreign.diff.tar.gzip` [in the specification](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#media-types): _"Layer", as a gzipped tar that should never...

Thank you for investigating this. I've also tried to fix the `LayerSources` problem locally, but unfortunately ended with the same issue as you :(

Any update on this, please? It would be very convenient if jib defaults fallback to settings from the `application` plugin. I'm also willing to prepare a PR if it's desired...

@sschuberth No, sorry, We don't use jib as it doesn't support Windows containers.