Chanseok Oh

Never mind. I managed to install Docker on Windows on GCE and checked these myself. For testing purposes, I think we can just ignore `LayerSources` and keep moving forward. These...

I tested building Windows images after ignoring `LayerSources`. Unfortunately, Jib doesn't seem to build correct Windows images. I was getting a bizarre error with both `jib:dockerBuild` and `jib:buildTar`. Someone on...

I've seen that Windows image layer tarballs have [PAX extension headers](https://en.wikipedia.org/wiki/Tar_(computing)#POSIX.1-2001/pax) to store some file metadata. ``` tar: Ignoring unknown extended header keyword 'LIBARCHIVE.creationtime' tar: Ignoring unknown extended header keyword...

The hard conclusion is that Jib doesn't support building Windows images. It just doesn't work for many many reasons.

Sure thing! Will be interesting to see if it works. (I expect it will.)

But probably we will replace 16 with 17 (instead of just adding 17) when it gets out. For efficiency, we don't want to test on every Java version. Probably only...

Sure, go ahead. I was just mentioning that when 17 comes out, we will probably drop 16.

It's not clear at the moment if switching to GSON is a good idea.

Sorry, let me clarify and document why. JSON processing is a critical part of Jib, and my main concern is the comment I left in the linked doc: > From...

I'm starting to question if the proposed do-HEAD-then-GET is needed for practical purposes (although I haven't looked into the Docker registry protocol.) If HEAD does not return 2xx for the...