Talk for CRIneta. Explains how Docker works and why it is so awesome. Additonal notes http://chrisortman.com/2015/06/02/docker-is-awesome/

1. Docker

2. Chris Ortman
University of Iowa
@chriso
chrisortman

3. Jerry
Steele
• Historic
2008
floods
begat
epic
cooperation
between
civic
leaders,
business,
universities,
community
colleges,
and
startups
• Making
“We
Create
Here”
meaningful
&
accessible

4. http://j.mp/tc-slack

6. Docker is Awesome

7. 1. Install and run any application with a single
command
2. GIT for servers
3. Executable setup documentation
4. Isolate development environments and tools

8. Key Components
Registry Image
pull
Container
run
Image
commit
push
Dockerfilebuild

9. XML CONFIGURATION

10. Key Component: Registry
Registry is a storage location where you can
pull and push preconfigured images that are
ready to go.
An example is DockerHub, but you can also
host your own pretty easily.

11. DEMO 1
applications

12. Homebrew
Boot2docker

13. –me
“It’s like git, but for servers”

14. docker run -d --publish 8080:8080 cptactionhank/atlassian-jira

15. Key Component: Image
Image is a readonly template that contains
your operating system files.
You can create new images by commiting your
changes to a container.

16. DEMO 2
images

17. Executable setup documentation

18. Key Component: Dockerfile
Dockerfile is a Makefile for your image.

19. –Wayne Mack c2wiki http://c2.com/cgi/wiki?
TestsAreAnExecutableSpecification
“The key advantage of a test set as proposed in
TestFirstDesign as a specification is that it is
unambiguously verifiable against the code. ”

20. DEMO 3
rvm-base dockerfile

21. Isolation

22. Key Component: Container
Container is your virtualized operating
system.
It uses namespaces, control groups, and
union file systems to provide isolation for
applications.

23. docker@boot2docker:~$ df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 1.8G 94.5M 1.7G 5% /
tmpfs 1002.1M 324.0K 1001.8M 0% /dev/shm
/dev/sda1 18.2G 6.8G 10.4G 40% /mnt/sda1
cgroup 1002.1M 0 1002.1M 0% /sys/fs/cgroup
none 464.8G 299.6G 165.1G 64% /Users
/dev/sda1 18.2G 6.8G 10.4G 40% /mnt/sda1/var/lib/docker/aufs
none 18.2G 6.8G 10.4G 40% /mnt/sda1/var/lib/docker/aufs/mnt/
431abd58c10b5560fee38b4dab8f6121f2f5b3f9475298e90b184caa423dd369
none 18.2G 6.8G 10.4G 40% /mnt/sda1/var/lib/docker/aufs/mnt/2342b6aa2e395dd9dd
root@2342b6aa2e39:/# df -h
Filesystem Size Used Avail Use% Mounted on
none 19G 6.9G 11G 40% /
tmpfs 1003M 0 1003M 0% /dev
shm 64M 0 64M 0% /dev/shm
/dev/sda1 19G 6.9G 11G 40% /etc/hosts
tmpfs 1003M 0 1003M 0% /proc/kcore
tmpfs 1003M 0 1003M 0% /proc/timer_stats
daemon@431abd58c10b:/var/local/atlassian/jira$ df -h
Filesystem Size Used Avail Use% Mounted on
none 19G 6.9G 11G 40% /
tmpfs 1003M 0 1003M 0% /dev
shm 64M 0 64M 0% /dev/shm
/dev/sda1 19G 6.9G 11G 40% /etc/hosts

24. DEMO 4
containers, data volumes, and links

25. What we’ve learned
• Download and run pre-configured applications
• Create images and share them
• Persist data
• Connect containers

26. • Registry is a storage location where you can pull
and push preconfigured images that are ready to
go.
• Image is a readonly template that contains your
operating system files.
• Dockerfile is a Makefile for your image.
• Container is your virtualized operating system.

27. Registry Image
pull
Container
run
Image
commit
push
Dockerfilebuild

28. http://j.mp/tc-slack
docker

29. Questions??
@chriso
chrisortman