Docker is an open platform for developers and system administrators to build, ship and run distributed applications. Using Docker, companies in Jordan have been able to build powerful system architectures that allow speeding up delivery, easing deployment processes and at the same time cutting major hosting costs. George Khoury shares his experience at Salalem in building flexible and cost effective architectures using Docker and other tools for infrastructure orchestration. The result allows them to easily and quickly move between different cloud providers.

1. Docker in Production
Upgrade your infrastructure.
Downgrade your cost.

2. ● Previously
● Software Engineer at SAP.
● iOS Instructor for an MIT summer course.
● Currently
● Student at the German Jordanian University.
● DevOps Engineer at Salalem.
● Future
● Planning to pursue a degree in education research and innovation.
About Me

3. Salalem Careers
● Salalem is looking for talented people in
various fields.
● If you are interested, please send your CV
to careers@salalem.com.

4. Containers

5. Outline
● The Virtual World
● What is Docker?
● Why use Docker?
● Building Blocks
● Docker Image
● Docker Container
● Docker Components
● Docker Toolbox
● Orchestration

6. The Virtual World

7. The Virtual World
● Virtual machines (VMs) are an abstraction of
physical hardware turning one server into
many servers.
● The hypervisor allows multiple VMs to run
on a single machine.
● Each VM includes a full copy of an operating
system, one or more apps, necessary
binaries and libraries - taking up tens of GBs.
● VMs can also be slow to boot.

8. What is Docker?

9. What is Docker?
● Docker is a software platform that allows you to build, test,
and deploy applications quickly.
● Standardized units called containers.
● Containers have everything the software needs to run
including libraries, system tools, code, and runtime.

10. Why use Docker?

11. Why use Docker?
● Ship more software, faster.
● Standardize operations.
● Runs on all major Linux distributions.
● Even runs on Windows!
● Secure your infrastructure.
● Isolated applications.
● Seamlessly move between providers or hosts.
● Save money.

12. Building Blocks - Images

13. Building Block - Docker Image
● An image is a lightweight, stand-alone,
executable package of a piece of
software.
● Contains code, runtime, system tools,
system libraries, settings, etc.
● Containerized software will always run
the same, regardless of the
environment.

14. Building Block - Docker Image
● An image is the template for a container.
● Built using UnionFS (Union Filesystem).
● Images are built by stacking layers on a
base image.
● Collections of images are stored/shared
in registries like Docker Hub.

15. Dockerfile
● A Dockerfile contains a list of instructions.
● Each instruction provides the docker engine
with the information needed to build an image
layer.
● Every Dockerfile must include the FROM
instruction to specify the base image.
● 1 instruction = 1 layer
● How many layers should we have?
● How do we order the instructions?

16. How to build a Docker Image?
● docker build is used to create
and image or “container template”.
● The docker engine parses the
Dockerfile, executes each instruction
and builds the corresponding layer.
● docker build -t myimage .
● Relative to the Dockerfile.

17. Building Blocks - Containers

18. Building Block - Docker Container
● Containers are running images.
● Containers are stateless “VMs”.
● How do we handle persistence?
● Distributed access to data?
● Multiple containers can run on the
same machine, and share resources.

19. Image vs. Container

20. How to run a Docker Container?
● We use the docker run to create running
instances of an image or “container”.
● The Docker Engine create a new instance of
the container.
● You can also provide additional arguments to
the run command.
● Volumes.
● Networks.
● Environment variables.
● Exposed and mapped ports.

21. Docker Components

23. Additional Tools in the Docker Toolbox
Docker Compose Kitematic Docker Engine Docker Registry

24. Orchestration

25. What is Orchestration?
● An application is typically multi-tier in its
architecture.
● We need a way to “schedule” and monitor
the lifecycle of containers.
● Containers are ephemeral.
● How do we persist data?
● How do we isolate containers into their
own networks?

26. Why do you need Orchestration?
● An orchestrator plays two main roles:
● Manage lifecycle
● Create new containers.
● Remove old / erroneous ones.
● Upgrade containers.
● Manage configuration
● Manage networks, volumes,
secrets, environment variables, etc.

28. Kubernetes - K8s
● Open-source container-orchestration system
for automating deployment, scaling, and
management of containerized applications.
● Scalable and very robust design patterns.
● Originally designed by Google.
● Interest in K8s has grown substantially.
● Choice of industry (Github for example).
● Many IT vendors started offering K8S
services.

29. Kubernetes - Contributions
15%
3%
4%
5%
10%
30%
33%
Independent
Google
Red Hat
Huawei
ZTE
IBM
Other

30. But…

31. Orchestration - Rancher as an Alternative
● Open-source container management platform.
Written in Go.
● Combines everything an organization needs to adopt
and run containers in production.
● Built on Kubernetes, easier to use.
● Main advantages:
● Run K8s everywhere.
● Multi-cluster Management.
● Centralized Policy Management.
● Workload Management.
● No vendor lock-in.

32. Orchestration - Rancher as an Alternative

33. Questions?

34. Thank you!