estargz: support lossless compression #453
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
moby/buildkit#2352
Currently, eStargz writer (
estargz.Writer
) rewrites tar headers of the original tar so it's not possible to recover the original tar blob from the result eStargz. This lossy behaviour can be problematic when the client needs to convert tar to eStargz and then recover the original tar from the result eStargz.For solving this issue, this commit adds
AppendTarLossLess
API toestargz.Writer
. This allows creating eStargz without changing the original tar blob.estargz.Unpack
API enables to decompress the eStargz and get the original tar blob.Note that this losslessness implies a limitation that the writer cannot support compressing a tar that contains a file named
stargz.index.json
because estargz cannot be created without overwriting that file. When the caller appends an eStargz blob to the writer, it should be decompressed to a tar usingestargz.Unpack
API.cc @tonistiigi
Thank you for the discussion.