The website uses cookies. By using this site, you agree to our use of cookies as described in the Privacy Policy.
I Agree
blank_error__heading
blank_error__body
Text direction?

Enable to pass additional handler on pull for stargz-based remote snapshots #1431

Conversation

Copy link
Contributor

Recently, we started a non-core subproject stargz-snapshotter aiming to speed up pull operation and we are seeing performance improvement on containerd.Client's Pull operation as the following (measured on Github Actions with Docker Hub. please also see README for more details).

The benchmarking result on 288c338

We've implemented the fundamental features and stargz snapshotter passes critest with a patched version of CRI plugin. Now it's ready for being experimentally used on k8s-based workloads and seeking adoptabilities on it.

Stargz snapshotter is implemented as a standard proxy plugin but because it queries layer contents to the registry it requires containerd clients (including CRI plugin) to pass additional information (image ref and layer digest) for each pull operation through an image handler.

This commit enables to use stargz-based remote snapshots through CRI optionally, by integrating the image handler with CRI. You can test this patch with this node image, which is tested using critest.

Measure
Measure
Related Notes
Get a free MyMarkup account to save this article and view it later on any device.
Create account

End User License Agreement

Summary | 3 Annotations
Now it's ready for being experimentally used on k8s-based workloads and seeking adoptabilities on it
2020/08/20 10:31
image ref and layer digest
2020/08/20 10:31
Enable to use snapshotter through containerd CRI plugin containerd/stargz-snapshotter#74
2020/08/20 10:33