Container orchestration in production in Docker - Step-by-Step Execution

Process Flow - Container orchestration in production

Define container images

↓

Create container specs

↓

Deploy to orchestration platform

↓

Platform schedules containers

↓

Monitor container health

↓

Scale containers up/down

↓

Handle failures & restart

↓

Update containers with zero downtime

This flow shows how container orchestration manages container deployment, scaling, health, and updates automatically in production.

Execution Sample

Docker

docker service create --name webapp --replicas 3 nginx

docker service ls

docker service ps webapp

docker service scale webapp=5

This code creates a service with 3 nginx containers, lists services, shows container tasks, then scales the service to 5 containers.

Process Table

Step	Command	Action	Result/Output
1	docker service create --name webapp --replicas 3 nginx	Create a service named 'webapp' with 3 nginx containers	Service 'webapp' created with 3 replicas
2	docker service ls	List all running services	ID NAME MODE REPLICAS IMAGE xyz webapp replicated 3/3 nginx:latest
3	docker service ps webapp	Show tasks (containers) for 'webapp'	ID NAME NODE DESIRED STATE CURRENT STATE abc webapp.1 node1 Running Running 2 minutes def webapp.2 node2 Running Running 2 minutes ghi webapp.3 node3 Running Running 2 minutes
4	docker service scale webapp=5	Scale 'webapp' service to 5 containers	webapp scaled to 5 replicas
5	docker service ls	List services after scaling	ID NAME MODE REPLICAS IMAGE xyz webapp replicated 5/5 nginx:latest
6	docker service ps webapp	Show updated tasks for 'webapp'	ID NAME NODE DESIRED STATE CURRENT STATE abc webapp.1 node1 Running Running 5 minutes def webapp.2 node2 Running Running 5 minutes ghi webapp.3 node3 Running Running 5 minutes jkl webapp.4 node1 Running Running 1 minute mno webapp.5 node2 Running Running 1 minute
7	docker service update --image nginx:1.21 webapp	Update service to new image version	Service 'webapp' updated to image nginx:1.21 with rolling update
8	docker service ps webapp	Show tasks during update	Some tasks restarting with new image, old tasks stopping
9	docker service ls	Final service state	ID NAME MODE REPLICAS IMAGE xyz webapp replicated 5/5 nginx:1.21
10	Exit	All containers running updated image, scaling and update complete	Orchestration successful

💡 All containers are running the updated image with desired replicas; orchestration tasks complete.

Status Tracker

Variable	Start	After Step 1	After Step 4	After Step 7	Final
replicas	0	3	5	5	5
image_version	none	nginx:latest	nginx:latest	nginx:1.21	nginx:1.21
service_status	none	created	scaled	updating	running updated

Key Moments - 3 Insights

Why does the number of replicas increase after the scale command?

Because the 'docker service scale' command changes the desired number of container replicas from 3 to 5, as shown in execution_table step 4 and 5.

How does the orchestration platform update containers without downtime?

It performs a rolling update by restarting containers one by one with the new image, keeping others running, as seen in steps 7 and 8.

What happens if a container fails during orchestration?

The platform automatically restarts the failed container to maintain the desired state, though this is implied in the flow and not shown explicitly in the table.

Visual Quiz - 3 Questions

Look at the execution table at step 4. What does the command do?

A Creates a new service with 5 replicas

B Scales the existing service to 5 replicas

C Deletes the service named webapp

D Updates the service image to nginx:1.21

💡 Hint

Check the 'Action' and 'Result/Output' columns at step 4 in the execution_table.

At which step does the service image version change?

A Step 1

B Step 4

C Step 7

D Step 9

💡 Hint

Look at the 'Command' and 'Result/Output' columns describing image update in the execution_table.

According to variable_tracker, what is the number of replicas after step 7?

A 5

B 0

C 3

D 7

💡 Hint

Check the 'replicas' row and the 'After Step 7' column in variable_tracker.

Concept Snapshot

Container orchestration manages multiple containers automatically.
Use commands like 'docker service create' to deploy.
Scale with 'docker service scale' to adjust replicas.
Update images with 'docker service update' for zero downtime.
Orchestration handles failures and keeps desired state.

Full Transcript

Container orchestration in production means managing many containers automatically. First, you create a service with a set number of container replicas. The orchestration platform schedules these containers on nodes. You can scale the number of containers up or down with a simple command. When updating the container image, the platform performs a rolling update to avoid downtime by restarting containers one at a time. It also monitors container health and restarts any that fail to keep the service running smoothly. This process ensures your application stays available and updated without manual intervention.