CPU limits and reservations in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding CPU Reservations in Docker

What does setting a CPU reservation in a Docker container do?

A Disables CPU usage for the container

B Limits the container to never use more than the reserved CPU share

C Guarantees the container will always get the reserved CPU share even if the host is busy

D Sets a soft limit that reserves CPU cycles for the container but does not restrict usage above it

💡 Hint

Think about what 'reservation' means in real life, like reserving a seat but not limiting others from using more if available.

CPU reservation in Docker is a soft guarantee. It reserves CPU cycles for the container but does not prevent it from using more if available. It ensures minimum CPU availability but does not limit maximum usage.

💻 Command Output

intermediate

Output of Docker Run with CPU Limit

What is the effect of running this command?

docker run --cpus=0.5 alpine top

A The container can use up to 50% of one CPU core

B The container is limited to 0.5 CPU cores but can burst above if available

C The container is guaranteed 0.5 CPU cores minimum

D The container will use exactly 0.5 CPU cores at all times

💡 Hint

Consider what '--cpus' means as a limit, not a reservation.

The '--cpus=0.5' flag limits the container to use at most half of one CPU core. It cannot exceed this limit but may use less.

❓ Troubleshoot

advanced

Troubleshooting CPU Limit Not Enforced

A Docker container is started with --cpu-shares=512 but it uses more CPU than expected. What is a likely cause?

A The host has multiple CPU cores, so the container can use more than one core

B The container is using CPU shares instead of CPU quota, so limits are not enforced

C Docker does not support CPU limits on the host operating system

D The CPU limit flag was ignored because the container is running in privileged mode

💡 Hint

Check if CPU quota or CPU shares are being used for limiting CPU.

CPU shares provide relative weighting but do not enforce strict limits. If CPU quota is not set properly, the container can exceed expected CPU usage.

🔀 Workflow

advanced

Configuring CPU Limits and Reservations in Docker Compose

Which snippet correctly sets a CPU limit of 1.5 CPUs and a CPU reservation of 0.5 CPUs in a Docker Compose file?

Docker

services:
  app:
    image: myapp
    deploy:
      resources:
        limits:
          cpus: '1.5'
        reservations:
          cpus: '0.5'

A

limits:
  cpus: '1.5'
reservations:
  cpus: '0.5'

B

limits:
  cpus: 1.5
reservations:
  cpus: 0.5

C

limits:
  cpus: 1
reservations:
  cpus: 1

D

limits:
  cpus: '0.5'
reservations:
  cpus: '1.5'

💡 Hint

Check the string format and values for limits and reservations.

The correct syntax uses strings for CPU values and sets limits higher than reservations to reserve less CPU than the max allowed.

✅ Best Practice

expert

Best Practice for Setting CPU Reservations in Production

What is the best practice when setting CPU reservations for containers in a production environment?

A Avoid setting CPU reservations to let the container use any available CPU freely

B Set CPU reservations equal to CPU limits to guarantee exact CPU usage

C Set CPU reservations lower than CPU limits to ensure minimum guaranteed CPU while allowing bursts

D Set CPU reservations higher than CPU limits to prioritize the container

💡 Hint

Think about balancing guaranteed resources and flexibility.

Setting CPU reservations lower than limits guarantees minimum CPU availability but allows containers to use more CPU when available, improving resource utilization.