Alert setup for container health in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding container health checks

Which of the following best describes the purpose of a HEALTHCHECK instruction in a Dockerfile?

A It specifies the network ports that the container exposes.

B It sets the container's resource limits like CPU and memory usage.

C It defines a command that Docker runs to test if the container is working properly.

D It installs monitoring software inside the container.

💡 Hint

Think about how Docker knows if a container is healthy or not.

The HEALTHCHECK instruction tells Docker how to test the container's health by running a command inside it periodically.

💻 Command Output

intermediate

Interpreting Docker container health status

What is the output of the following command if the container named webapp is healthy?

docker inspect --format='{{.State.Health.Status}}' webapp

A healthy

B unhealthy

C starting

D exited

💡 Hint

The command shows the health status of the container.

The command prints the health status of the container. If the container is healthy, it outputs healthy.

🔀 Workflow

advanced

Setting up alerting for unhealthy containers

You want to receive an alert when a Docker container becomes unhealthy. Which workflow below correctly describes the steps to achieve this using Docker events and a simple script?

A Run <code>docker events</code> to listen for container health status changes, filter for 'unhealthy' events, then trigger an alert script.

B Use <code>docker ps</code> to list containers and manually check health status every hour.

C Configure the container to send email alerts directly from inside the container when unhealthy.

D Restart the container automatically without monitoring health status.

💡 Hint

Think about how to get real-time notifications from Docker.

Docker events can be used to listen for health status changes. Filtering for 'unhealthy' events allows triggering alerts automatically.

❓ Troubleshoot

advanced

Diagnosing why a container health check fails

A container's health check keeps failing even though the service inside is running fine. Which of the following is the most likely cause?

A The container has no network access.

B The container image is missing.

C Docker daemon is not running.

D The health check command is incorrect or does not return the expected exit code.

💡 Hint

Consider what the health check command does and how Docker interprets its result.

If the health check command is wrong or returns a non-zero exit code, Docker marks the container as unhealthy even if the service is running.

✅ Best Practice

expert

Choosing the best health check command for a web server container

Which health check command is the best choice to monitor a web server running inside a Docker container?

A ping -c 1 localhost

B curl -f http://localhost:80/ || exit 1

C ps aux | grep nginx

D echo 'healthy'

💡 Hint

Think about a command that verifies the web server is responding correctly.

Using curl -f checks if the web server responds with a successful HTTP status. Other options do not verify the web service properly.

Practice

1. What is the main purpose of setting up a health check for a Docker container?

easy

A. To automatically monitor if the container is working properly

B. To increase the container's CPU usage

C. To change the container's network settings

D. To delete the container after a fixed time

Solution

1. Step 1: Understand health check purpose

   Health checks are used to monitor if a container is running as expected.

2. Step 2: Identify correct purpose

   Among the options, only monitoring container health matches the purpose.

3. Final Answer:

   To automatically monitor if the container is working properly -> Option A

4. Quick Check:

   Health check purpose = monitor container health [OK]

Hint: Health checks watch container status automatically [OK]

Common Mistakes:

• Thinking health checks change container settings
• Confusing health checks with resource limits
• Assuming health checks delete containers

2. Which of the following is the correct syntax to add a health check command in a Dockerfile?

easy

A. HEALTHCHECK CMD curl -f http://localhost/ || exit 1

B. HEALTHCHECK RUN curl -f http://localhost/ || exit 1

C. HEALTHCHECK EXEC curl -f http://localhost/ || exit 1

D. HEALTHCHECK TEST curl -f http://localhost/ || exit 1

Solution

1. Step 1: Recall Dockerfile health check syntax

   The correct Dockerfile instruction is HEALTHCHECK followed by CMD and the command.

2. Step 2: Match syntax with options

   Only HEALTHCHECK CMD curl -f http://localhost/ || exit 1 uses HEALTHCHECK CMD which is valid syntax.

3. Final Answer:

   HEALTHCHECK CMD curl -f http://localhost/ || exit 1 -> Option A

4. Quick Check:

   Dockerfile health check uses HEALTHCHECK CMD [OK]

Hint: Use HEALTHCHECK CMD for health commands in Dockerfile [OK]

Common Mistakes:

• Using RUN instead of CMD in HEALTHCHECK
• Using EXEC or TEST which are invalid keywords
• Omitting HEALTHCHECK keyword

3. Given this Docker run command, what will be the health status if the container's health check command fails repeatedly?

docker run --rm --health-cmd='curl -f http://localhost/ || exit 1' --health-interval=5s nginx

medium

A. The container health status will be 'healthy' regardless of failures

B. The container health status will be 'unhealthy' after failures

C. The container will stop immediately on first failure

D. The container will restart automatically on failure

Solution

1. Step 1: Understand health check failure behavior

   If the health check command fails repeatedly, Docker marks the container as 'unhealthy'.

2. Step 2: Analyze options

   Only The container health status will be 'unhealthy' after failures correctly states the container becomes 'unhealthy' after failures.

3. Final Answer:

   The container health status will be 'unhealthy' after failures -> Option B

4. Quick Check:

   Failed health checks = 'unhealthy' status [OK]

Hint: Failed health checks mark container as unhealthy [OK]

Common Mistakes:

• Thinking container stops immediately on failure
• Assuming container restarts automatically on health failure
• Believing health status stays 'healthy' despite failures

4. You wrote this Dockerfile snippet but the health check is not working as expected:

HEALTHCHECK CMD curl http://localhost/ || exit 1

What is the likely problem?

medium

A. Health check commands cannot use curl

B. Using CMD instead of RUN in HEALTHCHECK

C. The exit code should be 0 on failure

D. Missing the '-f' flag in curl to fail on HTTP errors

Solution

1. Step 1: Understand curl behavior in health checks

   Without '-f', curl returns success even on HTTP errors, so health check may falsely pass.

2. Step 2: Identify correct fix

   Adding '-f' makes curl fail on HTTP errors, correctly marking container unhealthy.

3. Final Answer:

   Missing the '-f' flag in curl to fail on HTTP errors -> Option D

4. Quick Check:

   Use curl -f to detect HTTP failures in health checks [OK]

Hint: Add '-f' to curl for proper failure detection [OK]

Common Mistakes:

• Confusing CMD with RUN in HEALTHCHECK
• Thinking curl cannot be used in health checks
• Using exit 0 to indicate failure

5. You want to set up an alert system that triggers when a Docker container becomes unhealthy. Which approach correctly combines Docker health checks with alerting?

hard

A. Set the container to restart automatically without health checks

B. Only rely on Docker logs to detect container issues, no health checks needed

C. Use Docker HEALTHCHECK in the Dockerfile and monitor container health status with an external tool like Prometheus

D. Manually run health check commands inside the container every hour

Solution

1. Step 1: Combine health checks with monitoring tools

   Docker HEALTHCHECK defines how to test container health automatically.

2. Step 2: Use external monitoring for alerts

   Tools like Prometheus can watch Docker health status and trigger alerts when unhealthy.

3. Step 3: Evaluate other options

   Options B, C, and D miss automatic health monitoring or alerting integration.

4. Final Answer:

   Use Docker HEALTHCHECK in the Dockerfile and monitor container health status with an external tool like Prometheus -> Option C

5. Quick Check:

   Healthcheck + monitoring tool = alert setup [OK]

Hint: Combine HEALTHCHECK with monitoring tools for alerts [OK]

Common Mistakes:

• Ignoring health checks and relying only on logs
• Assuming restart policies replace health monitoring
• Doing manual checks instead of automated monitoring