Docker allows building, shipping and running applications as lightweight containers. It provides an isolated runtime environment for applications and their dependencies, allowing developers to easily deploy their code in a consistent manner across different environments. Operations teams also benefit from Docker as it standardizes the application lifecycle and deployment process, improving efficiency, quality and speed of continuous integration and deployment. Docker containers are more lightweight than virtual machines and provide better performance, density and portability.

1. Introduction to
Docker
Containerization is the new virtualization

2. who
engineer and operations chap
open source chap
funny accent
(photo by Jennie Rainsford)

3. other matters
author
http://www.jamesturnbull.net
hack-n-slash developer
https://github.com/jamtur01
pontification
http://www.kartar.net

4. The Docker Book
www.dockerbook.com

5. Who are you
folks?

6. So what is Docker?
Container virtualization
Build, pack, ship and run applications as containers
Build once, run in many places
Isolated and content agnostic

7. Some history

8. So why should I care?
Easy (and lightweight!) way to model reality
Devs care about their app, Ops cares about the containers
Golden images without the overhead

9. Why developers care...
A clean, safe, hygienic and portable runtime environment
No worries about missing dependencies, packages and other pain
points
Run each app in its own isolated container, so you can run various
versions of libraries and other dependencies
Automate testing, integration, packaging
Reduce/eliminate concerns about compatibility on different platforms

10. Why operations care...
Make the entire lifecycle more efficient, consistent, and repeatable
Increase the quality of code produced by developers
Eliminate inconsistencies between development, test, and production
environments
Support segregation of duties
Significantly improves the speed and reliability of continuous
deployment and integration

11. So why not VMs or Cloud?
Speed of deployment
Portability
Size aka cached layering FTW
Density & Performance
Cost

12. Technology Stack
Runs (for now) on most Linux distros
cgroups and namespacing
Device Mapper or AUFS or vfs or <pluggable in future>
lxc or <pluggable in future>

13. Technology Stack

14. Docker Basics
Image
Registry
Container

15. Building Docker images with a
Dockerfile
FO
RM
uut
bnu
MITIE JmsTrbl "ae@xml.o"
ANANR ae unul jmseapecm
RNatgtisal- aah2
U p-e ntl y pce
EVAAH_U_SRwwdt
N PCERNUE w-aa
EVAAH_U_RU wwdt
N PCERNGOP w-aa
EVAAH_O_I /a/o/pce
N PCELGDR vrlgaah2
EPS 8
XOE 0
ETYON [/s/bnaah2]
NRPIT "ursi/pce"
CD[-" "OERUD]
M "D, FRGON"

16. Building the image
$sd dce bid-=jmu0/pce".
uo okr ul t"atr1aah2

17. Pushing the image
$sd dce ps jmu0/pce
uo okr uh atr1aah2

18. Running the container
$sd dce rn- - 8 - /a/w/yp jmu0/pce
uo okr u d p 0 v vrwwmap atr1aah2

19. Questions?