Containerd - core container runtime component

Containerd - core container runtime component

• 1.
  Docker Spins OutCore Container Runtime Component DECEMBER 16, 2016 containerd Livestream
• 2.
  2 Ask questions onTwitter #containerd
• 3.
  3 Docker Extracts andDonates 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
• 4.
  Docker Engine =Container Platform for Complete Distributed App Lifecycle 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
• 5.
  Docker Engine =Container Platform for Complete Distributed App Lifecycle 5 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
• 6.
  containerd: What is aCore 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 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
• 9.
  9 User first, plumbinglater 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…
• 10.
  containerd’s Role inContainer Ecosystem 10
• 11.
  Benefit to InfrastructureOperators 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
• 12.
  Benefit to EndUsers 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.
  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.md API: https://github.com/docker/containerd/tree/master/api/ Roadmap: https://github.com/docker/containerd/blob/master/ROADMAP.md containerd Project Information
• 14.
  What is runc? 14 root_file_system container.json
• 15.
  Containerd and runc
• 16.
  Containerd Today
• 17.
  Containerd 1.0 (Q2,2017)
• 18.
  Containerd 1.0 inDocker (Q2, 2017)