icon-cookie
The website uses cookies to optimize your user experience. Using this website grants us the permission to collect certain information essential to the provision of our services to you, but you may change the cookie settings within your browser any time you wish. Learn more
I agree
blank_error__heading
blank_error__body
Text direction?

Startup Containers in Lightning Speed with Lazy Image Distribution on Containerd

Error
500
Our nimblest minds and quickest coders are scrambling to bring Medium back — so hold tight.
What can you do? Try refreshing this page or check Medium's status.

We’ve made changes to our Terms of Service and Privacy Policy. They take effect on September 1, 2020, and we encourage you to review them. By continuing to use our services, you agree to the new Terms of Service and acknowledge the Privacy Policy applies to you.

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 | 12 Annotations
accounts for 76%
2020/08/19 09:13
only 6.4%
2020/08/19 09:13
cold-start
2020/08/19 09:13
fetching base images during builds
2020/08/19 09:13
big images are unavoidable
2020/08/19 09:14
lazily pull container images
2020/08/19 09:14
download the entire image for starting containers
2020/08/19 09:24
each node and plug it into containerd
2020/08/19 09:28
lazily pulls stargz/node:13.13.0-esgz image
2020/08/19 09:29
it’s shorter than the original image
2020/08/19 09:29
container runtimes need to download and extract file entries from layer blob
2020/08/19 09:29
entry anymore.
2020/08/19 09:32