Aleksa Sarai

As an aside, since we are creating a new serialisation format (unless we reuse `casync`) we will need to implement several debugging tools because now you will no longer be...

@AkihiroSuda A few things: 1. It depends how you define "runtime". If you include everything about the machine that pulls the image, extracts the image, and the runs a container...

@flx42 > what was the argument against doing simply file-level deduplication? Small modifications of large files, or files that are *substantially* similar but not identical (think man pages, shared libraries...

@flx42 It should be noted that with this proposal there would **no longer be a need for layers** (because the practical deduplication they provide is effectively zero) though I think...

Funnily enough, Go 1.11 has changed the default `archive/tar` output -- something that having a canonical representation would solve. See #269.

@flx42 > You would need an overlay obviously, but that means you won't be able to leverage the CoW mechanism from the underlying filesystem (which might be fined grain) and...

Blog post on the `tar` issues is up. https://www.cyphar.com/blog/post/20190121-ociv2-images-i-tar

@tych0 > One small nit on this, but otherwise it looks like it might be useful to us. How close do you feel this is to merging? I've been chatting...

I haven't touched this in a while. I can try to revive my PoC using the CAS API -- what exactly did you want to get into containers/image? Switching to...

I feel the the only slight complication is going to be chunked uploads and downloads which this PoC didn't implement. I started working on a PoC of this, it shouldn't...