containerd/stargz-snapshotter v0.2.0

on GitHub

Notable Changes

• Fix that hardlink tar entries can come to the invalid position by optimization (#181)
• Fix that --no-optimize option isn't enabled (#185)
• Fix that snapshot cannot be referred by multiple containerd namespaces (#188)
• Fix the footer format for making it compatible with RFC1952 (#190)
  • ctr-remote's --stargz-only option is deprecated. Instead, use --no-optimize option for aquiring eStargz image without optimization.

Important Note about compatibility

#190 changed the footer format of eStargz in backward-incompatible way.

eStargz since this release isn't compatible with stargz and eStargz of v0.1.0 (and older).
Stargz Snapshotter v0.1.0 (and older) cannot recognize this v0.2.0 (and newer) eStargz image.
But please note that eStargz of v0.2.0 (and newer) is still compatible with current OCI/Docker images.

Thus:

• eStargz images provided by ctr-remote v0.2.0 (and newer) is still pullable (but non-lazy) by eStargz-agnostic runtimes (e.g. Docker).
• eStargz images provided by ctr-remote v0.2.0 (and newer) cannot be lazily pulled by the Stargz Snapshotter v0.1.0 (and older).
• Stargz Snapshotter v0.2.0 (and newer) can still lazily pull stargz/eStargz provided by ctr-remote v0.1.0 (and older).

Please upgrade Stargz Snapshotter when you use ctr-remote v0.2.0 (and newer).