First Moscow
Docker Meetup
26 02 2015
Fabrizio Soppelsa fsoppelsa@mirantis.com
A Docker meetup
Why a meetup
● Informal meeting of friends
● Technical discussions on Docker
● Openstack.ru is our event partner
Why Docker
Docker is an open-source engine that
automates the deployment of any
application as a lightweight, portable,
self-sufficient container that will run
virtually anywhere.
Virtual machines and Containers
In a nutshell
● Unified command interface/API to manage
containers - start, stop, pull, pause, commit
● The interactive Docker tutorial
https://www.docker.com/tryit/
● Docker exploits some of the Linux kernel
Implementation
● Building blocks: namespaces + cgroups
● Isolation: namespaces (filesystem, pids,
net, ipc, hostname, uids)
● Management: cgroups: process grouping
● libcontainer
Docker is made of...
● The Docker server and client
● Docker images
● Registries (i.e. the Docker Hub)
● Containers
Docker in the real world
★ Separation: PaaS and SaaS
★ Isolation: Shared hosting
★ Fast: Sandboxes
★ Easy: Software deployments
★ Repeatable: CI and testing
Why is it so f***ing popular
● Easy to use (basic features)
● Software isolation and portability
● Thousands of ready images
● Density
● Start-up and shut-down times
End of the virtualization age?
HET
Ecosystem
● Written mostly in Go
● The Dockerfile
● Shipyard and other UIs
● Orchestration tools
Community
1. Matthew Mosesohn (Mirantis)
Docker off the grid
2. Denis Zaitsev (Yandex)
Scaling the Docker Registry
3. Sergey Melikyan (Mirantis)
Docker and OpenStack Murano
4. Andrey Vagin (Parallels)
Libcontainer: Joining forces under one roof
5. Plan B: eer!
Today

Docker. General overview

  • 1.
    First Moscow Docker Meetup 2602 2015 Fabrizio Soppelsa fsoppelsa@mirantis.com
  • 2.
    A Docker meetup Whya meetup ● Informal meeting of friends ● Technical discussions on Docker ● Openstack.ru is our event partner
  • 4.
    Why Docker Docker isan open-source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere.
  • 5.
  • 6.
    In a nutshell ●Unified command interface/API to manage containers - start, stop, pull, pause, commit ● The interactive Docker tutorial https://www.docker.com/tryit/ ● Docker exploits some of the Linux kernel
  • 7.
    Implementation ● Building blocks:namespaces + cgroups ● Isolation: namespaces (filesystem, pids, net, ipc, hostname, uids) ● Management: cgroups: process grouping ● libcontainer
  • 8.
    Docker is madeof... ● The Docker server and client ● Docker images ● Registries (i.e. the Docker Hub) ● Containers
  • 9.
    Docker in thereal world ★ Separation: PaaS and SaaS ★ Isolation: Shared hosting ★ Fast: Sandboxes ★ Easy: Software deployments ★ Repeatable: CI and testing
  • 10.
    Why is itso f***ing popular ● Easy to use (basic features) ● Software isolation and portability ● Thousands of ready images ● Density ● Start-up and shut-down times
  • 11.
    End of thevirtualization age? HET
  • 12.
    Ecosystem ● Written mostlyin Go ● The Dockerfile ● Shipyard and other UIs ● Orchestration tools
  • 13.
  • 14.
    1. Matthew Mosesohn(Mirantis) Docker off the grid 2. Denis Zaitsev (Yandex) Scaling the Docker Registry 3. Sergey Melikyan (Mirantis) Docker and OpenStack Murano 4. Andrey Vagin (Parallels) Libcontainer: Joining forces under one roof 5. Plan B: eer! Today