Brussels / 1 & 2 February 2020


Lazy distribution of container images

Current implementation status of containerd remote snapshotter

The biggest problem of the OCI Image Spec is that a container cannot be started until all the tarball layers are downloaded, even though more than 90% of the tarball contents are often unneeded for the actual workload.

This session will show state-of-the-art alternative image formats, which allow runtime implementations to start a container without waiting for all its image contents to be locally available.

Especially, this session will put focus on CRFS/stargz and its implementation status in containerd ( The plan for BuildKit integration will be shown as well.


Photo of Akihiro Suda Akihiro Suda