Docker Meetup Rosenheim: Container Runtimes
0 likes•789 views
The document discusses various container runtimes, highlighting their features and functionalities. It categorizes runtimes into low-level (like runc and runhcs) and high-level daemons (like containerd and Docker), outlining their purposes and usage scenarios. Additional container engines such as rkt, cri-o, gvisor, and kata containers are also mentioned, emphasizing the diversity of options available in container technology.
Docker Meetup Rosenheim: Container Runtimes
- 1. Make Your Data Work For You Container Runtimes Nico Meisenzahl April 2019
- 2. @panagenda Consultant. @DockerRosenheim founder. Blogger, speaker & IBM Champion. Loves K8s, containers & automation. His desk is a ping pong table. Nico Meisenzahl @nmeisenzahl https://meisenzahl.org [email protected] https://panagenda.com/modernization [email protected]
- 3. Container Runtimes • Container Runtimes make our life easier by – abstracting OS calls – adding additional features • there are multiple types of Container runtimes – low-level runtimes → let’s call them “runtime” – high-level runtimes (not real runtimes ) → let’s call them “daemon” and “engine” • I will only mention some Container Runtimes 3
- 4. runC • lightweight & low-level Container Runtime for Linux/Unix • hosted by Open Container Initiative (OCI) • wraps and therefor abstracts linux tools like namespaces, chroot, … • allows you to run containers. full stop. • binary/CLI only (no daemon process) • more details – https://github.com/opencontainers/runc 4
- 5. containerd • Container Daemon for Linux/Unix and Windows • hosted by Cloud Native Computing Foundation (CNCF) • uses runC and runhcs (Windows) to run containers • adds lifecycle functions (Image/Storage management, Metrics, ...) • daemon process with CLI • not intended to be used by humans (think about Kubernetes) • more details – https://github.com/containerd/containerd 5
- 6. Docker • full-featured Container Engine for Linux/Unix and Windows • owned by Docker • uses containerd to run containers – since Docker 1.11 • adds features like – Volumes, Networking, ... – Orchestration (Swarm) – API – end-user Client and CLI • runs as daemon process (dockerd) 6
- 7. Big Picture (Docker, containerd, runC) http://www.studytrails.com/wp-content/uploads/2018/12/Docker_Architecture_hierarchy.png 7
- 8. But there are others, too • rkt • CRI-O • runhcs • gVisor • Kata Containers Still, this is not a complete list! 8
- 9. rkt “rocket” • Container Engine (including runtime and daemon) for Linux/Unix • started by CoreOS • hosted by Cloud Native Computing Foundation (CNCF) • built with security in mind • own Image format (ACI) but can also run OCI and Docker Images • the smallest unit is a pods • CLI only (no daemon) • more details – https://github.com/rkt/rkt 9
- 10. CRI-O • lightweight Container Daemon for Linux/Unix • started by RedHat • hosted by Cloud Native Computing Foundation (CNCF) • Open Container Initiative-based (OCI) implementation of Kubernetes Container Runtime Interface (CRI) • supports runC and Kata Containers • more details – https://github.com/cri-o/cri-o – https://github.com/kubernetes/community/blob/master /contributors/devel/sig-node/container-runtime-interface.md 10
- 11. runhcs • lightweight & low-level Container Runtime for Windows • “runC for Windows” • by Microsoft • binary/CLI only (no daemon process) • more details – https://docs.microsoft.com/de-de/virtualization/windowscontainers/deploy-contai ners/containerd 11
- 12. runsc aka gVisor • low-level Container Runtime for Linux 64-bit • adds a security layer by implementing a user-namespace kernel • by Google • used by Google for their Cloud offerings • supported containerd (and therefore Docker and Kubernetes) • more details – https://cloud.google.com/blog/products/gcp/open-sourcing-gvisor-a-sandboxed-c ontainer-runtime 12
- 13. kata-runtime aka Kata Containers • low-level Container Runtime for Linux/Unix • uses lightweight Virtual Machines to add another isolation layer – based on Intel Clear Container and Hyper runV – supports QEMU and Firekracker VMs • supports containerd and CRI-O (and therefore Kubernetes) • more details – https://github.com/kata-containers/runtime 13
- 15. Headquarters, Austria: panagenda GmbH (Ltd.) Schreyvogelgasse 3/10 AT 1010 Vienna Phone: +43 1 89 012 89 Fax: +43 1 89 012 89-15 E-Mail: [email protected] Headquarters, Germany: panagenda GmbH (Ltd.) Lahnstraße 17 DE 64646 Heppenheim Phone: +49 6252 67 939-00 Fax: +49 6252 67 939-16 E-Mail: [email protected] USA: panagenda Inc. 60 State Street, Suite 700 MA 02109 Boston Phone: +1 617 855 5961 Fax: +1 617 488 2292 E-Mail: [email protected] Germany: panagenda Consulting GmbH (Ltd.) Donnersbergstrasse 1 DE 64646 Heppenheim Phone: +49 6252 67 939-86 Fax: +49 6252 67 939-16 E-Mail: [email protected] The Netherlands: Trust Factory B.V. 11th Floor, Koningin Julianaplein 10 NL 2595 AA The Hague Phone: +31 70 80 801 96 E-Mail: [email protected] © 2007-2015 panagenda Make Your Data Work For You