Alert setup for container health in Docker - Step-by-Step Execution

Process Flow - Alert setup for container health

Start Container

↓

Define Healthcheck

↓

Container Runs Healthcheck Command

↓

Healthcheck Result: Success or Failure

↓

Docker Updates Container Health Status

↓

Monitoring Tool Queries Health Status

↓

If Unhealthy -> Trigger Alert

↓

Notify User or System

↓

End

This flow shows how Docker runs health checks on containers, updates their status, and triggers alerts if unhealthy.

Execution Sample

Docker

docker run -d --name myapp \
  --health-cmd='curl -f http://localhost/ || exit 1' \
  --health-interval=30s \
  --health-retries=3 \
  myapp-image

# Monitor health status

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

Runs a container with a health check command and inspects its health status.

Process Table

Step	Action	Healthcheck Command Result	Health Status	Alert Triggered
1	Container starts running	N/A	starting	No
2	Healthcheck runs first time	Success	healthy	No
3	Healthcheck runs second time	Success	healthy	No
4	Healthcheck runs third time	Failure	healthy	No
5	Healthcheck runs fourth time	Failure	healthy	No
6	Healthcheck runs fifth time	Failure	unhealthy	Yes - after 3 failures
7	Alert sent to user/system	N/A	unhealthy	Yes

💡 Alert triggered after 3 consecutive healthcheck failures, container marked unhealthy.

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
Health Status	starting	healthy	healthy	healthy	healthy	unhealthy	unhealthy
Failure Count	0	0	0	1	2	3	3
Alert Triggered	No	No	No	No	No	Yes	Yes

Key Moments - 2 Insights

Why does the alert only trigger after the third failure and not the first unhealthy status?

Because the healthcheck retries are set to 3, Docker waits for 3 consecutive failures before marking the container unhealthy and triggering the alert, as shown in rows 4-6 of the execution table.

What does the healthcheck command do in this setup?

It runs a simple curl command to check if the container's service is responding. Success means the service is healthy; failure means it is not, as seen in the 'Healthcheck Command Result' column.

Visual Quiz - 3 Questions

Look at the execution table, what is the health status after the second healthcheck run?

A starting

B unhealthy

C healthy

D unknown

💡 Hint

Check the 'Health Status' column at Step 3 in the execution table.

At which step is the alert first triggered according to the execution table?

A Step 6

B Step 4

C Step 2

D Step 7

💡 Hint

Look at the 'Alert Triggered' column and find the first 'Yes'.

If the health-retries were set to 1 instead of 3, when would the alert trigger?

A Never triggers

B After the first failure (Step 4)

C After the third failure (Step 6)

D At container start

💡 Hint

Refer to how failure count affects alert triggering in the variable_tracker.

Concept Snapshot

Docker container health alert setup:
- Use --health-cmd to define a test command
- Set --health-interval for check frequency
- Use --health-retries to allow failures before alert
- Docker marks container unhealthy after retries fail
- Monitoring tools query health status to trigger alerts

Full Transcript

This visual execution shows how Docker runs health checks on a container using a command like curl. The container starts with status 'starting'. Each health check runs periodically. Success results keep status 'healthy'. Failures increase a failure count. After 3 consecutive failures, Docker marks the container 'unhealthy' and triggers an alert. The alert notifies users or systems to take action. This process helps keep containers monitored and issues detected early.

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