docker architecture(version modified)

Presentation By:Mohammadreza Amini

Amir Arsalan

Autumn 2015IRAN OpenStack Users Group

Docker ArchitectureVersion Modified

Agenda


| Iran Community OpenStack.ir

● Docker Concept

● How Does Docker Work?

● Should know about Docker

● Docker vs VMs

● Docker vs lxc

● The underlying technology



Docker Concept

Docker is composed of following four components



● Docker Client and Daemon

● Images

● registries

● Containers

Docker Client and Daemon



Docker Daemon

the Docker daemon runs on a host machine. The user does not directly interact

with the daemon, but instead through the Docker client.

Docker Client

The Docker client, in the form of the docker binary, is the primary user interface to

Docker. It accepts commands from the user and communicates back and forth with

a Docker daemon.

Images



A Docker image is a read-only template.

Image type:

● Images that exist on register (docker hub)

● Images that can created with build

Registeries



Docker registries hold images. These are public or private stores from which you upload or

download images. The public Docker registry is provided with the Docker Hub.

Containers



Docker containers are similar to a directory. A Docker container holds everything that is

needed for an application to run. Each container is created from a Docker image.



How Does Docker Work?



Reference: https://docs.docker.com/article-img/architecture.svg

What happens when you run a container?



● Pulls the image

● Creates a new container

● Allocates a filesystem and mounts a read-write layer

● Allocates a network / bridge interface

● Sets up an IP address

● Executes a process that you specify

● Captures and provides application output



Should know about Docker



● Docker is not LXC

● Docker is not a Virtual machine Solution.

● Docker is not a configuration management system and is not a replacement for chef,

puppet, Ansible etc.

● Docker is not a platform as a service technology.

Things you should know about Docker:



Docker vs VMs



Reference: https://risingstack-blog.s3-eu-west-1.amazonaws.com/2015/05/hypervisor-based-virtualization.jpg



Reference: https://risingstack-blog.s3-eu-west-1.amazonaws.com/2015/05/os-virtualization.jpg



Docker vs lxc



Reference: https://www.flockport.com/lxc-vs-docker/



The underlying technology

Namespaces



Namespaces provides a layer of isolation: each aspect of a container runs in its own

namespace and does not have access outside it.

More Details: http://www.toptal.com/linux/separation-anxiety-isolating-your-system-with-linux-namespaces

Control Groups



Cgroups running applications in isolation is to have them only use the resources you want. This ensures

containers are good multi-tenant citizens on a host. Control groups allow Docker to share available

hardware resources to containers and, if required, set up limits and constraints. For example, limiting the

memory available to a specific container.

More Details: https://www.kernel.org/doc/Documentation/cgroups/cgroups.txt

Union File System



Union file systems, or UnionFS, are file systems that operate by creating layers, making them very

lightweight and fast. Docker uses union file systems to provide the building blocks for containers.

More Details: http://www.fsl.cs.sunysb.edu/docs/unionfs-tr/unionfs.pdf



Any Question?



Stay in Touch and Join Us:

● Home Page: OpenStack.ir

● Meetup age: Meetup.com/IranOpenStack

● Mailing List: [email protected]

● Twitter: @OpenStackIR , #OpenStackIRAN

● IRC Channel on FreeNode: #OpenStack-ir



Mohammadreza Amini

Linux Administrator

[email protected]

Amir Arsalan

Python Developer

[email protected]

Thank You

docker architecture(version modified)

Technology