Scaling services with replicas in Docker - Step-by-Step Execution

Process Flow - Scaling services with replicas

Start with 1 service instance

↓

Decide number of replicas

↓

Run docker service scale command

↓

Docker creates additional replicas

↓

All replicas running

↓

Load balancer distributes requests

↓

Service scales up or down as needed

This flow shows how Docker scales a service by creating multiple replicas and balancing requests among them.

Execution Sample

Docker

docker service create --name myweb nginx

docker service scale myweb=3

Create a web service with one replica, then scale it to 3 replicas.

Process Table

Step	Command	Action	Replicas Running	Result
1	docker service create --name myweb nginx	Create service with default 1 replica	1	Service 'myweb' created with 1 replica
2	docker service scale myweb=3	Scale service to 3 replicas	3	Service 'myweb' now has 3 replicas running
3	docker service scale myweb=1	Scale service down to 1 replica	1	Service 'myweb' scaled down to 1 replica

💡 Scaling commands complete; service replicas adjusted as requested

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
replicas	0	1	3	1

Key Moments - 2 Insights

Why does the service start with 1 replica by default?

By default, Docker creates a service with 1 replica as shown in Step 1 of the execution_table. This ensures the service is running before scaling.

What happens if you scale to fewer replicas than currently running?

As shown in Step 3, scaling down reduces the number of replicas by stopping extra instances, so the service runs only the requested number.

Visual Quiz - 3 Questions

Look at the execution_table, how many replicas are running after Step 2?

A 1

B 2

C 3

D 0

💡 Hint

Check the 'Replicas Running' column for Step 2 in the execution_table

At which step does the service scale down to 1 replica?

A Step 3

B Step 2

C Step 1

D None

💡 Hint

Look at the 'Command' and 'Action' columns in the execution_table for scaling down

If you run 'docker service scale myweb=5' after Step 3, what will happen to replicas?

A Replicas stay at 1

B Replicas increase to 5

C Replicas decrease to 0

D Service is deleted

💡 Hint

Scaling up increases replicas as shown in Step 2; scaling to 5 will create 5 replicas

Concept Snapshot

Scaling services with replicas in Docker:
- Use 'docker service create' to start a service (default 1 replica)
- Use 'docker service scale servicename=number' to change replicas
- Docker adds or removes containers to match the replica count
- Load balancer spreads requests across replicas
- Scaling up adds instances; scaling down removes them

Full Transcript

This lesson shows how to scale Docker services by changing the number of replicas. First, a service is created with one replica. Then, the 'docker service scale' command changes the number of replicas. Docker adds or removes containers to match the requested count. This helps handle more or fewer requests by running multiple instances of the service. The load balancer sends traffic to all replicas evenly. Scaling up means more replicas; scaling down means fewer. The execution table traces these steps with commands and replica counts.

Practice

1. What does scaling a Docker service with replicas do?

easy

A. Runs multiple copies of the service to handle more work

B. Deletes the service completely

C. Changes the service's network settings

D. Updates the Docker engine version

Solution

1. Step 1: Understand the purpose of replicas

   Replicas are copies of a service running simultaneously to share the workload.

2. Step 2: Identify the effect of scaling replicas

   Scaling increases or decreases the number of these copies to improve performance and availability.

3. Final Answer:

   Runs multiple copies of the service to handle more work -> Option A

4. Quick Check:

   Scaling = multiple copies [OK]

Hint: Scaling means running more copies of your service [OK]

Common Mistakes:

• Thinking scaling deletes the service
• Confusing scaling with network changes
• Assuming scaling updates Docker itself

2. Which is the correct command to scale a Docker service named webapp to 5 replicas?

easy

A. docker service scale webapp -replicas 5

B. docker scale service webapp 5

C. docker service scale webapp --replicas=5

D. docker service scale webapp=5

Solution

1. Step 1: Recall the correct syntax for scaling

   The correct syntax is docker service scale SERVICE_NAME=NUMBER.

2. Step 2: Match the syntax with the options

   docker service scale webapp=5 matches the exact syntax: docker service scale webapp=5.

3. Final Answer:

   docker service scale webapp=5 -> Option D

4. Quick Check:

   Correct syntax = docker service scale NAME=NUM [OK]

Hint: Use SERVICE_NAME=NUMBER format with docker service scale [OK]

Common Mistakes:

• Using wrong command order
• Adding extra flags not needed
• Using spaces instead of '='

3. Given the command docker service scale api=3, what will be the number of running containers for the api service?

medium

A. 3 containers

B. 1 container

C. 0 containers

D. Depends on the Docker version

Solution

1. Step 1: Understand the scale command effect

   The command sets the number of replicas to 3, so Docker runs 3 containers for the service.

2. Step 2: Confirm the number of containers

   Scaling to 3 means exactly 3 containers will be running for api.

3. Final Answer:

   3 containers -> Option A

4. Quick Check:

   Scale api=3 means 3 containers [OK]

Hint: Scale number equals running containers count [OK]

Common Mistakes:

• Assuming only 1 container runs by default
• Thinking scaling depends on Docker version
• Confusing replicas with CPU cores

4. You run docker service scale backend=two but get an error. What is the problem?

medium

A. The service name cannot be 'backend'

B. The number of replicas must be a numeric value

C. The command should be run as root user

D. Docker service scale does not support scaling

Solution

1. Step 1: Check the scale command syntax

   The replicas count must be a number, not a word.

2. Step 2: Identify the error cause

   Using 'two' instead of '2' causes a syntax error.

3. Final Answer:

   The number of replicas must be a numeric value -> Option B

4. Quick Check:

   Replicas must be numeric [OK]

Hint: Use digits, not words, for replica counts [OK]

Common Mistakes:

• Using words instead of numbers
• Assuming service name is invalid
• Thinking root user is required

5. You have a service app running with 2 replicas. You want to update it to 4 replicas but keep the service running without downtime. Which command should you use?

hard

A. docker service scale app 4

B. docker container run app --replicas 4

C. docker service update --replicas 4 app

D. docker service restart app --replicas 4

Solution

1. Step 1: Understand how to update replicas without downtime

   Using docker service update --replicas 4 app changes replicas smoothly.

2. Step 2: Compare options for scaling

   docker service scale can scale but docker service update is preferred for zero downtime updates.

3. Step 3: Identify incorrect commands

   docker container run and docker service restart do not scale replicas properly.

4. Final Answer:

   docker service update --replicas 4 app -> Option C

5. Quick Check:

   Use service update for zero downtime scaling [OK]

Hint: Use 'docker service update --replicas' to avoid downtime [OK]

Common Mistakes:

• Using docker service scale causing brief downtime
• Trying to run containers manually
• Restarting service instead of updating replicas