docker service is the new docker run Getting Started with Docker - - PowerPoint PPT Presentation

▶

Sep 11, 2022 330 likes •689 views

docker service is the new docker run Getting Started with Docker Clustering Mike Goelzer / mgoelzer@docker.com / @mgoelzer Docker Inc. docker service is the new docker run docker run nginx 2013-14 docker run -p 3375:2375 swarm ; 2014-15

SLIDE 1

docker service is the new docker run

Getting Started with Docker Clustering

Mike Goelzer / mgoelzer@docker.com / @mgoelzer Docker Inc.

SLIDE 2

docker service is the new docker run

docker run nginx docker run -p 3375:2375 swarm ; docker run -H :3375 nginx

Swarm Mode in Docker Engine

docker swarm init ; docker service create nginx

2013-14 2014-15 2016

SLIDE 3

Features Walkthrough

SLIDE 4

Engine

Swarm Mode

$ docker swarm init

SLIDE 5

Engine

Swarm Mode

$ docker swarm init $ docker swarm join <IP of manager>:2377

Engine

SLIDE 6

Engine Engine Engine Engine Engine Engine

Swarm Mode

$ docker swarm init $ docker swarm join <IP of manager>:2377

SLIDE 7

Engine Engine Engine Engine Engine Engine

Services

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 frontend:latest

mynet

SLIDE 8

Engine Engine Engine Engine Engine Engine

Services

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 frontend:latest

$ docker service create --name redis --network mynet redis:latest

mynet

SLIDE 9

Engine Engine Engine Engine Engine Engine

Node Failure

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 frontend:latest

$ docker service create --name redis --network mynet redis:latest

mynet

SLIDE 10

Engine Engine Engine Engine Engine Engine

Node Failure

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 frontend:latest

$ docker service create --name redis --network mynet redis:latest

mynet

SLIDE 11

Engine Engine Engine Engine Engine

Desired State ≠ Actual State

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 frontend:latest

$ docker service create --name redis --network mynet redis:latest

mynet

SLIDE 12

Engine Engine Engine Engine Engine

Converge Back to Desired State

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 frontend:latest

$ docker service create --name redis --network mynet redis:latest

mynet

SLIDE 13

Engine Engine Engine Engine Engine

Scaling

$ docker service update --replicas 6 frontend

mynet

SLIDE 14

Engine Engine Engine Engine Engine

Scaling

$ docker service update --replicas 10 frontend

mynet

SLIDE 15

Engine Engine Engine Engine Engine

Global Services

$ docker service create --mode=global --name prometheus prom/prometheus

mynet

SLIDE 16

Engine Engine Engine Engine Engine

Constraints

Engine

docker daemon --label com.example.storage="ssd" docker daemon --label com.example.storage="ssd"

SLIDE 17

Engine Engine Engine Engine Engine

Constraints

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 --constraint engine.labels.com.example.storage==ssd

frontend:latest

Engine

docker daemon --label com.example.storage="ssd" docker daemon --label com.example.storage="ssd"

SLIDE 18

Engine Engine Engine Engine Engine

Constraints

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 --constraint engine.labels.com.example.storage==ssd

frontend:latest $ docker service update --replicas 10 frontend

Engine

docker daemon --label com.example.storage="ssd" docker daemon --label com.example.storage="ssd"

SLIDE 19

HEALTHCHECK --interval=5m --timeout=3s

-retries 3

CMD curl -f http://localhost/ || exit 1 Check web server every 5 minutes, require < 3 sec latency. >= 3 consecutive failures sets unhealthy state Coming soon: health checks in official images

Container Health Check in Dockerfile

SLIDE 20

Routing Mesh

Operator reserves a

swarm-wide ingress port (8080) for myapp

Every node listens on 8080
Container-aware routing mesh

can transparently reroute traffic from Worker3 to a node that is running container

Built in load balancing into the

Engine

DNS-based service discovery

:8080

User accesses myapp.com:8080

:8080 :8080

frontend frontend

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 frontend:latest

frontend

SLIDE 21

Routing Mesh: Published Ports

Operator reserves a

swarm-wide ingress port (8080) for myapp

Every node listens on 8080
Container-aware routing mesh

can transparently reroute traffic from third node to a node that is running container

Built in load balancing into the

Engine

DNS-based service discovery

:8080

User accesses myapp.com:8080

:8080 :8080

frontend frontend

$ docker service create --replicas 3 --name frontend --network mynet

p 8080:80 frontend_image:latest

frontend

SLIDE 22

Secure by default with end-to-end encryption

Out-of-the-box TLS

encryption and mutual auth

Automatic cert rotation
External or self-signed

root CA

Cryptographic node

identity

Certificate Authority TLS Certificate Authority TLS Certificate Authority TLS TLS TLS TLS

SLIDE 23

Scale: 2,000 Nodes and Counting

For now: community testing, crowd-sourced nodes, not funded by

Docker

Credit to: Chanwit Kaewkasi, Suranaree University of

Technology (SUT), Thailand

Results:

○ 2,384 nodes ○ 96,287 containers ○ Manager CPU/memory ≲15% ○ Test stopped because 3rd-party monitoring failed

https://github.com/swarm2k/swarm2k

@chanwit

SLIDE 24

Deep Dive: Topology

SLIDE 25

Node Node Node Node Node Node

Topology

Node Node Node Node Node Node

SLIDE 26

Node Node Node Node Node Node

Topology: roles

Node Node Node Node Node Node

Manager Worker

SLIDE 27

Node Node Node Node Node Node

Topology: roles

Node Node Node Node Node Node

Manager Worker

Each Node has a role
Roles are dynamic
Programmable Topology

SLIDE 28

Topology: scaling model

Manager Manager Manager Worker Worker Worker Worker Worker Worker

SLIDE 29

Topology: High Availability

Manager Manager Manager Worker Worker Worker Worker Worker Worker

Leader Follower Follower

SLIDE 30

Topology: High Availability

Manager Manager Manager Worker Worker Worker Worker Worker Worker

Leader Follower Follower

SLIDE 31

Topology: High Availability

Manager Manager Manager Worker Worker Worker Worker Worker Worker

Follower Follower Leader

SLIDE 32

Topology: High Availability

Manager Manager Manager Worker Worker Worker Worker Worker Worker

Follower Follower Leader

SLIDE 33

DEMO

SLIDE 34

Victor Vieux vieux@docker.com / @vieux Mike Goelzer mgoelzer@docker.com / @mgoelzer