The document discusses how Docker can be used to package applications for deployment in remote data centers. Some key benefits of Docker include having executable documentation, determinism in runtime environments, and being able to ship only code changes rather than entire applications. However, deploying to remote data centers can be challenging due to factors like equipment age and geopolitical issues. Docker addresses this by enabling the use of immutable environments and images, which makes reasoning about application states in remote locations easier.

1. Docker offshore –
packaging applications
for hard to reach data-centers
Joern Barthel
Berlin, 23.10.2014

2. devopsdays 2014
Berlin
2

3. devopsdays 2014
Berlin
3

4. Benefits
 Executable documentation
 “What you check in is what you
get”
 Determinism for your runtime
environment
devopsdays 2014
Berlin
4

5. devopsdays 2014
Berlin
5

6. devopsdays 2014
Berlin
6

7. devopsdays 2014
Berlin
7

8. devopsdays 2014
Berlin
8

9. Not so fast, not so reliable
 Age of vessel & equipment
 Geolocation
 Geopolitics
devopsdays 2014
Berlin
9

10. Solution: immutable
environments
 Docker!
devopsdays 2014
Berlin
10

11. Docker in a nutshell
 Golang client & server
 Containers virtualize perspective
not hardware
devopsdays 2014
Berlin
11

12. Immutable images
 Build
 Name and distribute
 Run (as containers)
devopsdays 2014
Berlin
12

13. What’s in a
build?
 Commands build layers
 Union of changes
 Environment
 Immutable filesystem
 Caching rules
devopsdays 2014
Berlin
13

14. What’s in a
name?
 Repository of images
 Projects names, git revisions,
versions etc.
 Implicit pull & push
devopsdays 2014
Berlin
14

15. What’s in a container?
 Parameterized process
 Sharing ports, volumes
 Restricting stuff
 Mutable filesystem
devopsdays 2014
Berlin
15

16. Easier determinism
 Same image everywhere
 Easier reasoning about state of
remote datacenter
devopsdays 2014
Berlin
16

17. Ship changes
 Save bandwidth by shipping only
incremental diffs
 Release or patch
devopsdays 2014
Berlin
17

18. Simplified packaging
 Concrete provisioning
 No custom packaging for LTS
environments
devopsdays 2014
Berlin
18

19. Separation of concerns
 Regulations!
 Developers build images
 Operators run containers
devopsdays 2014
Berlin
19

20. Summary
 Being immutable helps with
reasoning
 Concrete vs. abstract reduces
complexity
devopsdays 2014
Berlin
20