Brandon Mitchell

> I'm trying to understand the delta the MitM solution and no-network in practice. For the MitM, the build can access any resource and it's simply recorded. For no-network, the...

The `regctl image export` does not modify the image, that would change the digest. The compression of the layers is done by the image builder, and that would be the...

To verify, does changing the image, and its digest, matter for your use case? What is the purpose of uncompressing content and recompressing it in this scenario?

> which inner layers is uncompressed, to archive maximum compress ratio, or able to modify image locally. I'm still not understanding the use case. - Where are the images coming...

> > * Is filesystem usage important before the xz compression is run at the source or after the image is uncompressed at the destination? > > Since probably you...

> I finally got how to use this `regctl image mod`, it will be ok if I can use this to uncompress layers, which seems not present yet. Thanks for...

This should be supported now, though my recommendation is to hold off for zstd support to get added and use that rather than an uncompressed export that's later compressed with...

FYI, #732 was just added to support zstd compression of the layers.

> The meaning of `application/cose` will be that every other client (different from Notary and not implemented according to the Notary specification) will be able to pull the signature and...

Hi @hdonnay, what's your use case? Perhaps there are better options or this can turn into a feature request. `RWFS` is an interface, so if you implement the interface, it...