This document introduces Docker containers as a way to package applications and their dependencies to run in isolation and be portable across different environments. It discusses problems with current provisioning approaches that can result in unknown server states and notes Docker containers aim to define everything required to run an application in a self-contained package that is lightweight like a process. The document recommends exploring Docker and waiting for supporting tooling to emerge, and provides links for further information.

1. An introduction
By Emil Stenqvist, @svammel

2. Some background

3. Things have changed

4. The Matrix From Hell

5. When programming...
1. Avoid globals
2. Keep separate concerns separate (SoC)
3. Be explicit about dependencies

6. State and determinism

7. Containment and
reproducibility

8. Typical Provisioning
1. Define your server state using e.g. Chef
2. Run on a “dirty” server
3. Resulting state is unknown, but hopefully
works.

9. We run our software on operating
systems conceived in 1980.

10. Ship software as a whole

13. A container full of EC2

14. What if we could create containers that:
●
●
●
●
●
Contained our application and its dependencies
Were transferable
Ran in isolation
Ran everywhere
Were as light-weight as processes

15. Hands-on with Docker

16. Discover Docker
1. http://docker.io — community is great
2. Play with it — I’ve only shown my use-cases
3. Wait for the tooling to emerge — it’s an explosion
waiting to happen.
4. Check out CoreOS

17. Questions?
● github.com/emilisto/docker-intro
● Who was the guy again? @svammel