Delivered to Charlotte Junior Devs, August 2017

1. Intro to Containers
It’s Complicated

2. Hi, I’m @bigfleet (aka Jim Van Fleet)

4. Containers are DevOps
But not all of it

5. “Why are
we going
so slow?”

6. b6n: AWS’s “weird uncle” Ben Black

8. Container Anatomy
“Build, Ship, Run” implies a lot of tech

11. Containers in
Development
VM’s with benefits

12. docker run -p 6379:6379
redis
Run redis without installing it on your machine
Your machine can connect on 6379

13. echo 'info' | redis-cli
# Server
redis_version:3.2.9
process_id:1

14. OHAI Dockerfile
Containers come from images.
Images are created by Dockerfiles.

16. Quo Vadis Dockerfile
• Install system libraries and configure them
• Bundle your gems
• Perform your gradle or maven build
• Install node, npm, webpack, perform a webpack build
• Set up a complicated process tree
• whatevs really, but most importantly…

17. Dockerfile
is version controlled
System and code are under developer control

18. Interlude
You wanted a banana

19. A service is a composition
Images are created by Dockerfiles.
Containers are created from images.
Containers are networked with each other via docker-compose.yml

21. A composition is a
contract
Security
Ops
QA
Etc.

22. Devs can conjure simpler
commitments.
A barer composition is another point of agency.

23. Where do images come
from?
Images are created by Dockerfiles.
Images are distributed via registries.

24. Containers in Testing
Docker : Jenkins :: Peanut Butter : Chocolate

25. CI/CD automates
commitments.
Ops can begin to securely provide secrets.
QA can sign off on an image that can’t have its code changed.
Images can be scanned by security before distribution.
Monitoring can inject agents.
Operating environments (QA, staging) get updated with new code.

26. OHAI Jenkinsfile
This process is getting translated from humans as its implemented.
Jenkinsfile is in version control as well…
…alongside a docker-compose.yml very easily

27. node("docker") {
docker.withRegistry('<<your-docker-registry>>',
'<<your-docker-registry-credentials-id>>') {
git url: "<<your-git-repo-url>>",
credentialsId: '<<your-git-credentials-id>>'
sh "git rev-parse HEAD > .git/commit-id"
def commit_id = readFile('.git/commit-id').trim()
println commit_id
stage "build"
def app = docker.build "your-project-name"
stage "publish"
app.push 'master'
app.push "${commit_id}"
}
}

28. Containers in Operation
Leaning in to distributed systems

29. Containers were born at
scale.
They have an opinionated approach to the matter.
Container images need to be designed accordingly.
Operations staff responsibilities change significantly.

30. Basics of a Swarm

31. Basics of a Swarm

32. Service atop a Swarm

33. Service atop a Swarm

34. Service atop a Swarm

35. Service atop a Swarm

36. So What?

37. Stacks of Frontiers
• Containerizing workloads by writing Dockerfiles
• Placing services into composition for smoke testing or runtime
• Installing Docker EE, Jenkins agents, etc. (automated or otherwise)
• Writing Jenkins pipelines and pipeline libraries
• Custom workflow integrations to satisfy stakeholders
• …and we’ve only talked about one technology among many!

38. Barriers to a lucrative
career are low.

39. Thanks
If you want a sequel, let me know.
Which part was most interesting?