Since the first 1.0 release in late 2017, containerd has earned a large list of new adopters, including two major public clouds and recently graduated as a CNCF project. It’s a major milestone for the project that provides a “boring core container runtime,” demonstrating that it has reached a high level of maturity.
Phil Estes, IBM Distinguished Engineer for IBM Cloud division, gave an update on the status of containerd and shared a glimpse to the roadmap. In 2018, containerd and its CRI plugin was marked as general availability 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 A-list adopters since last year including AWS Firecracker VMM, Kata Containers, Alibaba PouchContainer; Microsoft is also contributing and hardening the complete Windows container support in the containerd 1.2 release.
- If you’re ready to dive in, try the quickstart guide
- Take a look at the Github repo
- Join the Slack channel
- Or read the documentation
Watch the full 20-minute video from the recent talk given at FOSDEM.