Why resource limits matter in Docker - Why It Works

Introduction

When you run applications in containers, they can use too much memory or CPU and slow down or crash your computer. Setting resource limits helps keep your system stable by controlling how much CPU and memory each container can use.

When you want to prevent one container from using all the CPU and slowing down other containers.

When you need to avoid a container crashing the host by using too much memory.

When running multiple containers on the same machine and you want to share resources fairly.

When testing how your app behaves under limited CPU or memory conditions.

When deploying apps in production to ensure reliability and avoid unexpected crashes.

Commands

This command runs a container named 'limited-container' with a memory limit of 100 megabytes and CPU limit of half a CPU core. It runs the 'top' command to show running processes inside the container.

Terminal

docker run --name limited-container --memory 100m --cpus 0.5 busybox top

Expected Output

top - 00:00:00 up 0 min,  0 users,  load average: 0.00, 0.00, 0.00

Tasks: 1 total,   1 running,   0 sleeping,   0 stopped,   0 zombie

%CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND

  0.0  0.0   1232   512 pts/0    R+   00:00   0:00 top

→

--memory - Limits the maximum memory the container can use

→

--cpus - Limits the number of CPU cores the container can use

This command shows the current CPU and memory usage of the 'limited-container' to verify the limits are in effect.

Terminal

docker stats limited-container --no-stream

Expected Output

CONTAINER ID   NAME               CPU %     MEM USAGE / LIMIT     MEM %     NET I/O     BLOCK I/O     PIDS

abcdef123456   limited-container  0.00%     2.5MiB / 100MiB      2.50%     1.2kB / 0B  0B / 0B       1

→

--no-stream - Shows a single snapshot of resource usage instead of continuous updates

This command stops and removes the 'limited-container' to clean up after the test.

Terminal

docker rm -f limited-container

Expected Output

limited-container

→

-f - Forces removal of the container even if it is running

Key Concept

If you remember nothing else from this pattern, remember: setting resource limits on containers prevents them from using too much CPU or memory and keeps your system stable.

Common Mistakes

Not setting any resource limits when running containers

Containers can consume all available CPU or memory, causing the host or other containers to slow down or crash.

Always use --memory and --cpus flags to set reasonable limits based on your app's needs.

Setting resource limits too low without testing

Your container might not have enough resources to run properly and could crash or behave unexpectedly.

Test your app with different limits to find a balance between resource use and performance.

Confusing --memory with swap limits

By default, --memory limits only RAM, and containers can still use swap space, which might cause unexpected memory use.

Understand Docker's memory and swap settings and configure swap limits if needed for stricter control.

Summary

Use --memory and --cpus flags to limit container resource usage.

Check resource usage with docker stats to verify limits.

Remove containers after testing to keep your environment clean.

Practice

1. Why is it important to set resource limits like --memory and --cpus when running Docker containers?

easy

A. To prevent one container from using too many resources and slowing down the whole system

B. To make containers run faster by giving them unlimited resources

C. To allow containers to access the host's hardware directly

D. To automatically update the container software

Solution

1. Step 1: Understand resource limits purpose

   Resource limits control how much CPU and memory a container can use to avoid overloading the host system.

2. Step 2: Identify the effect of limits

   Setting limits prevents one container from hogging all resources, keeping the system stable for all containers.

3. Final Answer:

   To prevent one container from using too many resources and slowing down the whole system -> Option A

4. Quick Check:

   Resource limits = prevent overload [OK]

Hint: Limits protect system by capping container resource use [OK]

Common Mistakes:

• Thinking limits make containers faster
• Believing containers get direct hardware access
• Confusing resource limits with software updates

2. Which of the following is the correct syntax to limit a Docker container's memory to 500MB and CPU to 1.5 cores?

easy

A. docker run --memory=500MB --cpus=1.5 myimage

B. docker run --mem=500 --cpu=1.5 myimage

C. docker run --memory-limit=500MB --cpu-limit=1.5 myimage

D. docker run --memory 500MB --cpus 1.5 myimage

Solution

1. Step 1: Recall Docker resource limit flags

   The correct flags are --memory for memory and --cpus for CPU limits.

2. Step 2: Check syntax correctness

   docker run --memory=500MB --cpus=1.5 myimage uses correct flags with equal signs and units, which is the proper Docker syntax.

3. Final Answer:

   docker run --memory=500MB --cpus=1.5 myimage -> Option A

4. Quick Check:

   Correct flags and syntax = docker run --memory=500MB --cpus=1.5 myimage [OK]

Hint: Use --memory and --cpus with = and units [OK]

Common Mistakes:

• Using incorrect flag names like --mem or --cpu
• Omitting equal signs between flag and value
• Not specifying units for memory

3. What will happen if you run this command?

docker run --memory=100m --cpus=0.5 busybox sh -c "stress --vm 1 --vm-bytes 200m --vm-hang 0"

medium

A. The container will ignore the limits and run with full resources

B. The container will run normally without any issues

C. The container will use more CPU than allowed but not memory

D. The container will be killed because it tries to use more memory than allowed

Solution

1. Step 1: Analyze memory limit and stress command

   The container is limited to 100MB memory but tries to allocate 200MB, which exceeds the limit.

2. Step 2: Understand Docker behavior on limit breach

   Docker kills containers that exceed memory limits to protect the host system.

3. Final Answer:

   The container will be killed because it tries to use more memory than allowed -> Option D

4. Quick Check:

   Memory limit exceeded = container killed [OK]

Hint: Exceeding memory limit kills container [OK]

Common Mistakes:

• Assuming container runs normally despite limit
• Thinking CPU limits affect memory usage
• Believing limits are ignored

4. You set --memory=256m on a container, but it still crashes with an out-of-memory error. What is the most likely cause?

medium

A. The container is using swap memory which is unlimited by default

B. The container is running on a host with too much free memory

C. The memory limit flag was misspelled and ignored

D. The CPU limit is too low causing memory errors

Solution

1. Step 1: Check common mistakes with memory limits

   If the flag is misspelled, Docker ignores it and no limit is applied, causing crashes.

2. Step 2: Rule out other options

   Swap is limited separately, host memory does not cause container crashes, and CPU limits do not cause memory errors.

3. Final Answer:

   The memory limit flag was misspelled and ignored -> Option C

4. Quick Check:

   Misspelled flag = no limit applied [OK]

Hint: Check flag spelling if limits don't work [OK]

Common Mistakes:

• Ignoring flag spelling errors
• Confusing CPU limits with memory issues
• Assuming host memory size affects container limits

5. You want to run multiple containers on a server with 4 CPU cores and 8GB RAM. How should you set resource limits to keep the system stable?

hard

A. Do not set any limits and rely on Docker to manage resources automatically

B. Assign each container a CPU limit of 1 core and memory limit of 2GB

C. Set CPU limit to 4 cores and memory to 8GB for each container

D. Give each container unlimited CPU and memory to maximize performance

Solution

1. Step 1: Calculate fair resource distribution

   With 4 cores and 8GB RAM, dividing resources evenly means 1 core and 2GB per container if running 4 containers.

2. Step 2: Understand why limits matter for stability

   Setting limits prevents any container from using all resources, keeping the system responsive and stable.

3. Final Answer:

   Assign each container a CPU limit of 1 core and memory limit of 2GB -> Option B

4. Quick Check:

   Even resource limits = system stability [OK]

Hint: Divide total resources fairly among containers [OK]

Common Mistakes:

• Giving unlimited resources causing overload
• Setting limits higher than host capacity
• Not setting limits and risking crashes