Containerd report january 2017 for Kubenetes sig node meeting

1. JANUARY,
2017
containerd
Extracting Docker’s core container runtime

2. 2
Docker Extracts and Donates containerd to
Accelerate Innovation Across the Ecosystem
● Open source Docker’s core container runtime component into community project
○ Expansion of original containerd adding more Docker Engine functionality
○ Provides all the core primitives to manage containers on Linux and Windows hosts
○ Will use the OCI standard and be fully OCI compliant when 1.0 available
● Docker & other leading container systems to use containerd as core runtime
component
○ containerd used in millions of production Docker Engines since April 2016 in Docker 1.11
○ Provide a “boring” infrastructure component
● Built by Docker with input from largest cloud providers for project success
● Commitment to donate to a neutral, open foundation in Q1 2017

3. Docker Engine = Container Platform for
Complete Distributed App Lifecycle
3
Docker Differentiators
SwarmKit
Containerd
InfraKit
Container Orchestration
Core Container Runtime
Infrastructure
Docker
API
Docker
CLI
Docker
Compose
Docker
Build
Auth Docker
Content
Trust
Docker
Distribution
Plugins
Storage
Networking

4. 4
Docker Differentiators
SwarmKit
Containerd
InfraKit
Container Orchestration
Core Container Runtime
Infrastructure
Docker
API
Docker
CLI
Docker
Compose
Docker
Build
Auth Docker
Content
Trust
Docker
Distribution
Plugins
Storage
Networking
Docker Commercial Platform Docker Datacenter
Docker Engine = Container Platform for
Complete Distributed App Lifecycle

5. containerd:
What is a Core Container Runtime?
5
Component that provides
core primitives to manage
containers on a host
Currently 0.2.4 with
target for 1.0 feature set
(including OCI in Q2
2017)
Features
Container execution
and supervision
Image distribution
Network Interfaces & Mgmt
Local storage
Native plumbing level API
“Boring” infrastructure
component for container
infrastructure providers
Receiving upstream
patches from
infrastructure operators

6. containerd’s Role in Container Ecosystem
9

7. containerd and Kubernetes
10

8. Benefit to Infrastructure Operators and Providers
11
“Boring infrastructure” for the container ecosystem
• Limited feature scope that stabilizes over time
• A commitment to a stable API
• A community-defined release process which emphasizes quality over new features
• A reasonable LTS policy comparable to infrastructure projects of similar maturity
Collaborative community driven project run in the open
Designed for extensibility to work with all leading container
orchestrators
Branded separately from Docker, so as not to cause
undue benefit to a single commercial entity

9. Benefit to End Users
12
Greater collaboration
and component re-
use among vendors
to avoid
fragmentation
Allows for greater
vendor innovation at
higher levels of the
stack
Multi-cloud
portability
Allows Docker
platform to innovate
at its accelerated
pace

10. What is runc?
13
root_file_system
container.json

11. Containerd and runc

12. Containerd Today

13. Containerd 1.0 (Q2, 2017)

14. Containerd 1.0 in Docker (Q2, 2017)

15. 18
Containerd Livestream Recap https://blog.docker.com/2017/01/containerd-livestream-recap/
Containerd Summit at Docker office 02/23/2017
Repo open for comments / collaboration / contribution
https://github.com/docker/containerd
Sign up for
February summit
More project details:
Architecture: https://github.com/docker/containerd/blob/master/design/architecture.md
API: https://github.com/docker/containerd/tree/master/api/
Roadmap: https://github.com/docker/containerd/blob/master/ROADMAP.md
containerd Project Information

16. containerd reports
19 https://github.com/docker/containerd/tree/master/reports