Alert setup for container health in Docker - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of setting up alerts for container health?

Alerts notify you when a container is unhealthy or stops working properly, so you can fix issues quickly and keep your app running smoothly.

beginner

Which Docker command helps check the health status of a container?

The command docker ps shows container status, including health if a health check is defined.

intermediate

How do you define a health check in a Dockerfile?

Use the HEALTHCHECK instruction with a command that tests the container's health, for example:

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

intermediate

What tool can you use to send alerts based on Docker container health status?

You can use monitoring tools like Prometheus with Alertmanager, or Docker events combined with scripts to send alerts via email or messaging apps.

beginner

Why is it important to have a health check command that returns proper exit codes?

Because Docker uses the exit code to decide if the container is healthy (0) or unhealthy (non-zero). This helps Docker and alert systems know the real status.

What does the Docker HEALTHCHECK instruction do?

A Runs a command inside the container to test its health regularly

B Stops the container if it uses too much memory

C Updates the container image automatically

D Creates a backup of the container data

The HEALTHCHECK instruction runs a command inside the container to check if it is working properly.

Which exit code should a health check command return to indicate the container is healthy?

A 0

B 1

C 2

D Any non-zero number

Exit code 0 means success, so Docker treats the container as healthy.

How can you view the health status of running Docker containers?

A docker logs

B docker images

C docker ps

D docker build

The 'docker ps' command shows running containers and their health status if health checks are defined.

Which tool is commonly used to send alerts based on container health metrics?

A Docker Compose

B Git

C Kubernetes Dashboard

D Prometheus with Alertmanager

Prometheus collects metrics and Alertmanager sends alerts when conditions like unhealthy containers occur.

What is a simple way to trigger an alert when a Docker container becomes unhealthy?

A Restart the container manually every hour

B Monitor Docker events and send notifications when health status changes

C Delete the container logs

D Increase container CPU limits

Monitoring Docker events for health status changes allows automated alerts when a container becomes unhealthy.

Explain how to set up a health check in a Docker container and why it is useful.

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

Describe a simple alerting approach for Docker container health using available tools.

Consider how you can get notified when a container stops working 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