The conversation

Lessons learnedExperience excerpt · English

I'm a maintainer of the Moby project (which is used to build the Docker Engine), and saw this post …

I'm a maintainer of the Moby project (which is used to build the Docker Engine), and saw this post got some attention, so let me try to outline some of the changes and motivation. Happy to answer questions if there's any. First of all, some history; the Docker Engine was a monolith daemon that provided many services; this worked well when using Docker as a standalone solution, but when used as runtime for Kubernetes, this wasn't ideal; many components were not designed for this purpose, which meant they had to be replaced / overridden with hacks to make it work. The containerd project was created to provide a more modular runtime for the container ecosystem, providing separate subcomponents (a containerd runtime, image/content storage) for the container ecosystem to build on. It was created "from scratch" with lessons learned over the Years, providing a modern foundation. …

Original discussionDocker 29 has changed its default image store for new installs85 source comments · at import
2

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

A_

Hey, just wanted to say I appreciate the containerd API, between the two it's much more performant to work against.

Full original
AW

Why store uncompressed layers? Surely decompression is fast enough that there's little gain in storing the decompressed layers?

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.