You’ve heard about Docker, maybe you use it already as a development environment for virtualising your project on your local machine. But running your application or website with Docker in production is a whole different deal. In this session you’ll get a deeper insight into working with Docker in practice. Starting with the 101 of concepts we’ll go through a practical scenario for hosting, automatically deploying and monitoring an application in production with recommendations for a variety of tools and services.

1. Docker in Production

2. Robert Lemke
CEO Flownative
Project Founder Neos
robert@flownative.com
@robertlemke

4. Docker
Toolbox
www.docker.com/docker-toolbox

5. Docker
Beta
beta.docker.com

7. A quick
Docker 101

15. Docker just for dev?
What are the benefits?

16. Containers are
Unix processes,
not lightweight
virtual machines.

17. One image per
application and its
dependencies.

18. site:
image: tianon/true
volumes:
- /application
application:
image: eu.gcr.io/flownative-beach/beach-php-application-
gateway:latest
ports:
- "8180:80"
- "8122:22"
volumes:
- ./.Docker/secrets:/secrets
- ./.Docker/configuration:/configuration
volumes_from:
- site
environment:
- BEACH_FLOW_BASE_CONTEXT=Development
- BEACH_APPLICATION_USER_SERVICE_ENABLE=false

19. what's different
in production?

20. monitoring
deployment
debugging
security
backup
storage

21. the host

22. which
operating
system
?

27. provisioning

28. Docker
Machine

31. resource "aws_instance" "www1" {
ami = "${lookup(var.amis, var.region)}"
availability_zone = "${var.region}a"
instance_type = "t2.micro"
subnet_id = "${aws_subnet.kubenet_craft.id}"
associate_public_ip_address = true
tags {
Name = "www1.${var.regioncode}.flownative.net"
}
}
resource "aws_route53_record" "kubemaster" {
zone_id = "${var.flownativenet_zone_id}"
name = "www1.${var.regioncode}"
type = "A"
ttl = "60"
records = [
"${aws_instance.www1.private_ip}"]
}

32. images

33. use your own
images

34. choose a
base image
security!
size
fitness

35. private
repositories
hub.docker.com
quay.io
Google Cloud
AWS
gitlab.com

36. sudo docker build -t beta.gcr.io/myproject/nginx:$BUILD_ID .
sudo docker tag -f beta.gcr.io/myproject/nginx:$BUILD_ID beta.gcr.io/myproject/nginx
sudo docker login -u _json_key -p "$(cat …json)" -e x@y.com https://beta.gcr.io
sudo docker push beta.gcr.io/myproject/nginx:latest
sudo docker push beta.gcr.io/myproject/nginx:$BUILD_ID

39. composition

40. Docker
Compose

41. decouple …
nginx:
image: flownative/nginx:latest
external_links:
- cargo_jenkins_1
ports:
- "443:443"
volumes:
- data/certs/STAR_flownative_com.key:/etc/nginx/certs/flownative/docker-registry/STAR_flownative_com.key
- data/certs/STAR_flownative_com-ssl-bundle.crt:/etc/nginx/certs/flownative/docker-registry/
STAR_flownative_com-ssl-bundle.crt
volumes_from:
- cargo_jenkins_1
restart: always
jenkins:
build: "docker-jenkins"
restart: always
volumes:
- data/jenkins:/var/jenkins_home
- /var/run/docker.sock:/var/run/docker.sock
- /usr/bin/docker:/usr/bin/docker
ports:
- "8080:8080"

42. deployment

43. #!/bin/bash
ssh ubuntu@foo.flownative.net "cd ~/docker; sudo docker-compose -p cargo -f docker-compose-nginx.yml stop"
ssh ubuntu@foo.flownative.net "cd ~/docker; sudo docker-compose -p cargo -f docker-compose-nginx.yml rm -f"
scp ./docker-compose-nginx.yml ubuntu@cargo.flownative.net:/home/ubuntu/docker/
ssh ubuntu@foo.flownative.net "cd ~/docker; sudo docker-compose -p cargo -f docker-compose-nginx.yml build"
ssh ubuntu@foo.flownative.net "cd ~/docker; sudo docker-compose -p cargo -f docker-compose-nginx.yml up -d"

44. How would you
design your
infrastructure if
you couldn’t
login? Ever.

45. scheduling

46. Docker
Cloud

47. Docker
Cloud

51. apiVersion: v1
kind: ReplicationController
metadata:
name: "neos-wwwneosio-elasticsearch-1"
spec:
replicas: 1
selector:
account: "neos"
project: "wwwneosio"
stage: "production"
type: "elasticsearch"
version: "1"
template:
metadata:
labels:
account: "neos"
project: "wwwneosio"
stage: "production"
type: "elasticsearch"
version: "1"
spec:
containers:
- name: elasticsearch
image: docker.flownative.com/flownative/elasticsearch:1
ports:
- containerPort: 9200
resources:
requests:
memory: "100Mi"
cpu: "10m"
limits:
memory: "800Mi"
cpu: "500m"
env:
- name: ELASTICSEARCH_CLUSTER_NAME
value: "neos-wwwneosio"

52. apiVersion: v1
kind: Service
metadata:
name: elasticsearch-628f1e05
labels:
account: "neos"
project: "wwwneosio"
stage: "production"
type: "elasticsearchmaster"
spec:
type: NodePort
ports:
- name: elasticsearchrestapi
port: 9200
targetPort: 9200
- name: elasticsearchtransport
port: 9300
targetPort: 9300
selector:
account: "neos"
project: "wwwneosio"
stage: "production"
type: "elasticsearchmaster"

55. service
discovery

57. persistent
data

58. host volume
network filesystem
cloud storages
data-only containers

59. monitoring

60. Docker stats
docker stats $(docker ps | awk '{if(NR>1) print $NF}')

64. tips&tricks

65. PaaS?
your own?

66. what do you want
to work on?
Host maintenance?

67. Where to start?

68. develop images locally
use Docker Compose
(deploy with a script + Docker Compose)
start using Docker Cloud / Giant Swarm
look into Kubernetes on Google Cloud
rehearse backup, monitoring, debugging
learn ~
Docker in Production

69. Containers will
fundamentally
change the way we
ship web
applications.

70. Containers will
fundamentally
change the way we
develop web
applications.

71. robert@flownative.com
www.flownative.com
@robertlemke
share your
thoughts