Introduction about Docker

1. Docker Introduction
github.com/phucnguyenvn

2. Agenda
1. Story
2. What is Docker
LinuX Container (LXC)
Docker Image
Docker Container
Docker Architecture & Basic command
Linking & Expose
Volume
Dockerfile
3. Demo
4. Docker advantages

3. The situation we
deploy PHP Projects!
that we feel HURT

4. PHP Version Requirement
Yii
CodeIgniter
DokuWiki
Drupal 6
Wordpress
There are so many
PHP Projects..
Phalcon
Symfony
Drupal 7
MediaWiki
Laravel
Joomla
Drupal 8

5. PHP Version Requirement
Yii 5.1+
CodeIgniter 5.1.6+
DokuWiki 5.2
Drupal 6 5.2.x
Wordpress 5.2.4+
But version
requirement are
different!?
Phalcon 5.3+
Symfony 5.3.3+
Drupal 7 5.2.5+
MediaWiki 5.3.2+
Laravel 5.4+
Joomla 5.4+
Drupal 8 5.4+

6. WHICH PHP VERSION
SHOULD I INSTALLED?
Yii 5.1+
CodeIgniter 5.1.6+
DokuWiki 5.2
Drupal 6 5.2.x
Wordpress 5.2.4+
But version
requirement are
different!?
Phalcon 5.3+
Symfony 5.3.3+
Drupal 7 5.2.5+
MediaWiki 5.3.2+
Laravel 5.4+
Joomla 5.4+
Drupal 8 5.4+

7. Multifarious Extension
apxs2, bcmath, bz2, calendar, cgi, cli, ctype,
dba, debug, dom, embed, exif, fileinfo, filter,
fpm, ftp, gcov, gd, gettext, hash, iconv, icu,
imap, intl, ipc, ipv6, json, kerberos, mbregex,
mbstring, mcrypt, mhash, mysql, openssl,
pcntl, pcre, pdo, pgsql, phar, posix, readline,
session, soap, sockets, sqlite, tidy, tokenizer,
xml_all, xmlrpc, zip, zlib

8. One server – multi projects
SERVER
App 1 App 2 App n.......

9. One server – multi projects
SERVER
App 1 App 2 App n.......
BUT DIFFERENT
REQUIREMENT

10. How to solve
problems?

11. That awesome!
But may it be more lightweight?

12. The Challenge

13. The Matrix from Hell

14. Cargo Transport Pre-1960

15. Also a Matrix from Hell

16. Solution:
Intermodal Shipping Container

17. Docker is a Container System for Code

18. Docker Eliminates the Matrix from Hell

19. Docker Eliminates the Matrix from Hell

20. Docker Trends

22. What is LXC?
• LinuX Containers
• Available since kernel 2.6.27
• Lightweight VM
• own process space
• own network interface
• SHARE kernel with host
• Run Linux within Linux

24. Why Docker Containers Lightweight?

25. Docker Image
• Read Only
• Don’t change
• Envionments
• Used to be container

26. Docker Container
• ReadWrite Layer
• Running Process
• Build with one or more images
• Commit change to create image

27. Relationship between
image and container
Image
(registry)
PULL
Image
(local)
Container
RUN
Container+CHANGE
COMMIT
PUSH

28. Docker architecture

29. Basic Command

30. Version
$ docker version

31. Info
$ docker info

32. Pull base image(s)
$ docker pull <image-name:tag>
image name

33. List images
$ docker images

34. Run
$ docker run <option> <image-name:tag> <command> <argument>
image name command argument

35. List container
$ docker ps -a

36. Running container

37. Running container
Ctlr + q to detach

38. Running container

39. Linking & Expose

40. Linking
LOCALHOST
PHP + Apache
Container
MySQL
Container
Localhost:80
Localhost:3306

41. Linking
LOCALHOST
PHP + Apache
Container
MySQL
Container
Localhost:80
Localhost:3306

42. Linking
LOCALHOST
PHP + Apache
Container
MySQL
Container
Localhost:80

43. Linking & Expose
image name
Linking
Expose port
$ docker run –p <host-name>:<host-port>:<container-port>

44. Volume

45. Volume
HOST
Volume directory
……..
CONTAINER
/var/www/html
……
Isolation

46. Volume
HOST
Volume directory
……..
CONTAINER
/var/www/html
……
How could we mount
container’s directory to host?

47. Volume
HOST
Volume directory
……..
CONTAINER
/var/www/html
……
Volume
• Real time changes
• Exist until container destroyed
• Can set RO mode

48. Volume
HOST
Volume directory
……..
CONTAINER A
/var/www/html
……
Volume
CONTAINER B
/var/www/html
……

49. Dockerfile
• Automatically build images and deploy
• Automated build on Docker Hub
• Easy to share and customize config

50. Docker Compose
• Define and run multi-container applications
• Specify images and configuration in a simple YAML file:
docker-compose.yml
• One command to get all running: docker-compose up

51. Demo

52. Demo
LOCALHOST
Wordpress +
Apache
Container
MySQL
Container
Localhost:80

53. Docker advantages

54. Docker advantages

55. Docker advantages

57. Docker advantages

58. Why Developers Care
Build once.. (finally) run anywhere*
• A clean, safe, hygienic, portable runtime environment for your app.
• No worries about missing dependencies, packages and other pain
points during subsequent deployments.
• Run each app in its own isolated container, so you can run various
versions of libraries and other dependencies for each app without
worrying.
• Automate testing, integration, packaging...anything you can script.
• Reduce/eliminate concerns about compatibility on different
platforms, either your own or your customers.
• Cheap, zero-penalty containers to deploy services. A VM without the
overhead of a VM. Instant replay and reset of image snapshots.
* "anywhere" means an x86 server running a modern Linux kernel
(3.2+ generally or 2.6.32+ for RHEL 6.5+, Fedora, & related)

59. Why Administrators Care
Configure once.. Run anything
• Make the entire lifecycle more efficient, consistent, and repeatable
• Increase the quality of code produced by developers.
• Eliminate inconsistencies between development, test, production,
and customer environments.
• Support segregation of duties.
• Significantly improves the speed and reliability of continuous
deployment and continuous integration systems.
• Because the containers are so lightweight, address significant
performance, costs, deployment, and portability issues normally
associated with VMs.

60. Resource & Reference
• Docs.docker.com
• Docker Cookbook
• Docker in Practice
• Katacoda.com

61. Thank you!

62. Q & A