Alert setup for container health in Docker - Commands & Configuration

Introduction

Containers can stop working or become unhealthy without you noticing. Setting up alerts helps you know immediately when a container has a problem so you can fix it quickly.

When you want to know if your web server container crashes or stops responding.

When you run a database container and need to be alerted if it stops working.

When you deploy multiple containers and want to monitor their health automatically.

When you want to avoid downtime by fixing container issues before users notice.

When you want to track container restarts to find unstable services.

Config File - docker-compose.yml

docker-compose.yml

version: '3.8'
services:
  my-app:
    image: nginx:1.23
    ports:
      - "8080:80"
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 5s

This file defines a service named my-app using the nginx image.

The healthcheck section tells Docker how to check if the container is working properly by trying to access its web page.

If the health check fails 3 times in a row, Docker marks the container as unhealthy.

Commands

This command starts the container defined in the docker-compose.yml file in detached mode, so it runs in the background.

Terminal

docker-compose up -d

Expected Output

Creating network "default" with the default driver

Creating my-app_1 ... done

→

-d - Run containers in the background (detached mode)

This command lists running containers so you can check if your container is up and see its status.

Terminal

docker ps

Expected Output

CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS                    PORTS                  NAMES

abc123def456   nginx:1.23     "/docker-entrypoint.…"   10 seconds ago   Up 8 seconds (healthy)    0.0.0.0:8080->80/tcp   my-app_1

This command shows detailed health status of the container named my-app_1 in JSON format so you can see if it is healthy or not.

Terminal

docker inspect --format='{{json .State.Health}}' my-app_1

Expected Output

{"Status":"healthy","FailingStreak":0,"Log":[{"Start":"2024-06-01T12:00:00Z","End":"2024-06-01T12:00:05Z","ExitCode":0,"Output":""}]}

→

--format - Format the output using a Go template for easier reading

This command shows recent health status events for the container to monitor changes and detect unhealthy states.

Terminal

docker events --filter 'container=my-app_1' --filter 'event=health_status' --since '10m'

Expected Output

2024-06-01T12:05:00.000000000Z container my-app_1 health_status: healthy

2024-06-01T12:10:00.000000000Z container my-app_1 health_status: unhealthy

→

--filter - Filter events by container and event type

→

--since - Show events only from the last 10 minutes

Key Concept

If you remember nothing else from this pattern, remember: Docker health checks let you automatically detect container problems and trigger alerts or actions.

Common Mistakes

Not defining a healthcheck in the Docker or docker-compose file.

Without a healthcheck, Docker cannot know if the container is working properly or not.

Always add a healthcheck section with a test command that verifies the container's main function.

Using a healthcheck command that always succeeds or never finishes.

This causes false healthy or stuck states, hiding real problems.

Use a simple, fast command that returns failure if the service is down, like a curl request to a local endpoint.

Ignoring the health status and not monitoring it regularly.

You won't know if the container becomes unhealthy and cannot fix issues quickly.

Use commands like docker inspect or docker events to watch health status and integrate alerts in your monitoring system.

Summary

Define a healthcheck in your docker-compose.yml to let Docker test container health automatically.

Start your container with docker-compose up -d and check its status with docker ps.

Use docker inspect and docker events to monitor health status and detect problems 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