Docker Spins Out Core Container Runtime Component

DECEMBER 16, 2016

containerd Livestream

2

Ask questions on Twitter#containerd

3

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

Docker Engine = Container Platform for Complete Distributed App Lifecycle

4

Docker Differentiators

SwarmKit

Containerd

InfraKit

Container Orchestration

Core Container Runtime

Infrastructure

DockerAPI

DockerCLI

DockerCompose

DockerBuild

Auth DockerContent

Trust

DockerDistribution

PluginsStorage

Networking

Docker Engine = Container Platform for Complete Distributed App Lifecycle

5

Docker Differentiators

SwarmKit

Containerd

InfraKit

Container Orchestration

Core Container Runtime

Infrastructure

DockerAPI

DockerCLI

DockerCompose

DockerBuild

Auth DockerContent

Trust

DockerDistribution

PluginsStorage

Networking

Docker Commercial Platform Docker Datacenter

containerd: What is a Core Container Runtime?

6

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 executionand supervisionImage distributionNetwork Interfaces & MgmtLocal storageNative plumbing level API

“Boring” infrastructure component for container infrastructure providers

Receiving upstream patches from infrastructure operators

9

User first, plumbing later

Obsess over your user’s problems. Spin out open components along the way.

React, GraphQL…

Webkit, Swift, LLVM…

Chromium, Tensorflow…

Hystrix, Hasgard…

containerd, notary, runC,

hyperkit…

containerd’s Role in Container Ecosystem

10

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

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

13

Livestream for Friday, December 16th - to register: www.docker.com

Repo open for comments / collaboration / contribution 12/14/16:https://github.com/docker/containerd

Sign up for February summit

More project details:

Architecture: https://github.com/docker/containerd/blob/master/design/architecture.mdAPI: https://github.com/docker/containerd/tree/master/api/Roadmap: https://github.com/docker/containerd/blob/master/ROADMAP.md

containerd Project Information

What is runc?

14

root_file_system container.json

Containerd and runc

Containerd Today

Containerd 1.0 (Q2, 2017)

Containerd 1.0 in Docker (Q2, 2017)