Phil Estes

It's been almost 10 years since the demonstration of the earliest Docker client at PyCon in 2013. While container capabilities and tooling existed prior to Docker, we can all agree that the last 10 years has seen an explosion of tools, integrations, and production services all built on container runtime technologies similar to that early Docker engine project.

Given that context, it's a good time to look around and survey the landscape of container developer tooling in use today. While Docker engine, and the companion Docker Desktop product are widely used, the creation of the OCI standards and the launching of the CNCF has allowed for a wide array of tools and projects that also provide developers tools and capabilities to create, build, and run containers and interoperate with container registries. In this talk we'll tour the current world of open source developer tools, including podman, the early simple containerd clients, nerdctl, and the advent of non-Linux platform support built alongside these tools, such as Rancher Desktop, Lima/colima, Finch, and Podman Desktop.

Attendees will learn a bit about each of the container developer tool platforms, what open source components they are built from, and how to see them in context with the other alternatives in this space. We'll demonstrate the similarities and differences, and show how thanks to the OCI specs, interoperability between these tools is guaranteed and that developers have significant choice when deciding what tools to use for local container development.

Over the past year, projects looking to extend and embed core container runtime functionality have looked to containerd and its clean API and extension points as a valuable resource. In this talk we'll look at the projects which have extended or embedded containerd for specific use cases and how containerd has enabled these uses via its design. We will also do a brief project update for the broader container ecosystem and community.

As containerd reaches its fourth birthday, it has already been adopted as a container runtime underneath Kubernetes in public cloud providers and various developer tools and platforms. In this talk we'll look deeper at the architecture choices and clean API layer which has enabled further use of containerd as an embedded and extensible runtime in additional projects, like Amazon's Firecracker integration, Kata's use of the v2 shim API, and Microsoft Azure's creation of the Teleport registry feature. We'll also look at in-flight work with CERN, Google, and others around remote "pre-seeded" snapshotters which allow for significant speedups in container startup time with special-case clusters like CERN's compute cloud.

Last year at FOSDEM, containerd was presented as a fairly new CNCF project which had just reached its 1.0 release a month prior. With two major releases since then and a large list of new adopters, including two major public clouds, containerd has continued to gain momentum as a project and this talk will provide an update on users, releases, and the future plans for containerd and its maturity as a core, open source container runtime.

Last year at FOSDEM, containerd was presented as a fairly new CNCF project which had just reached its 1.0 release a month prior. With two major releases since then and a large list of new adopters, including two major public clouds, containerd has continued to gain momentum as a project and this talk will provide an update on users, releases, and the future plans for containerd and its maturity as a core, open source container runtime.

In 2018, containerd and its CRI plugin was marked as GA for use in Kubernetes, followed by two major public clouds--Google's GKE and IBM Cloud's IKS--offering containerd as their managed Kubernetes cluster's runtime. Containerd continues to be used by all Docker releases, and Docker has plans to remove more code from the moby project and utilize stable features within containerd instead, furthering adoption of containerd's codebase.

Additionally, the attractive API and stability of containerd has brought quite a few new adopters since last year including AWS Firecracker VMM, Kata Containers, Alibaba PouchContainer, and Microsoft contributing and hardening the complete Windows container support in the containerd 1.2 release. Containerd has also proposed to be a "graduated" project in the CNCF and has received a full security audit which will be published soon.

Containerd, a minimal container runtime created out of the original Docker engine, has now been a Cloud Native Computing Foundation (CNCF) member project since March 2017. Intended for use not just by the Docker engine as a lower layer container runtime and management layer above an OCI compliant executor, the expectation is that Kubernetes will use containerd as well as other projects that need a straightforward, embeddable container runtime without vendor control or opinionated behavior.

This project update will overview how we arrived at a "containerd 1.0" feature complete state from the original containerd implementation, and how it is being embedded and used in various projects like "cri-containerd" for Kubernetes and the recent Docker engine releases. We'll also look at the ease with which containerd can be embedded via its client library to offer container lifecycle management to any broader application.

Containerd, a minimal container runtime created out of the original Docker engine, has now been a Cloud Native Computing Foundation (CNCF) member project since March 2017. Intended for use not just by the Docker engine as a lower layer container runtime and management layer above an OCI compliant executor, the expectation is that Kubernetes will use containerd as well as other projects that need a straightforward, embeddable container runtime without vendor control or opinionated behavior.

This project update will overview how we arrived at a "containerd 1.0" feature complete state from the original containerd implementation, and how it is being embedded and used in various projects like "cri-containerd" for Kubernetes and the recent Docker engine releases. We'll also look at the ease with which containerd can be embedded via its client library to offer container lifecycle management to any broader application.