Docker events monitoring - Commands & Configuration

Introduction

Sometimes you want to see what is happening inside Docker in real time. Docker events monitoring lets you watch actions like containers starting, stopping, or images being pulled. This helps you understand and troubleshoot Docker activity as it happens.

When you want to know immediately if a container crashes or stops.

When you are debugging why a container is restarting repeatedly.

When you want to audit what images are being pulled or removed on your system.

When you need to track network or volume changes related to Docker containers.

When you want to log Docker activity for security or compliance reasons.

Commands

This command shows Docker container start and stop events from the last 10 minutes. It helps you watch recent container activity live.

Terminal

docker events --filter event=start --filter event=stop --since 10m

Expected Output

2024-06-01T12:00:01.123456789Z container start 123abc456def (image=nginx:1.23, name=my-nginx)

2024-06-01T12:05:15.987654321Z container stop 123abc456def (image=nginx:1.23, name=my-nginx)

→

--filter - Filter events by type, like start or stop

→

--since - Show events only from a certain time ago

This command monitors only container 'die' events, which happen when a container stops unexpectedly. Useful for catching crashes.

Terminal

docker events --filter type=container --filter event=die

Expected Output

2024-06-01T12:10:30.123456789Z container die 789def123abc (image=redis:7.0, name=my-redis)

→

--filter - Filter events by container type and die event

This command shows image pull and remove events. It helps track when images are downloaded or deleted on your system.

Terminal

docker events --filter event=pull --filter event=remove

Expected Output

2024-06-01T12:15:00.000000000Z image pull sha256:abcdef1234567890

2024-06-01T12:20:00.000000000Z image remove nginx:1.23

→

--filter - Filter events by image pull and remove

Key Concept

If you remember nothing else from Docker events monitoring, remember: you can watch real-time Docker actions filtered by type to quickly understand what is happening.

Common Mistakes

Running 'docker events' without filters and expecting only container events.

Docker events include many types like network, volume, image, and container events, so output can be overwhelming.

Use --filter flags to narrow down events to only what you want to see.

Not using --since and watching events from the very start, causing too much output.

Without --since, the command streams all events from the daemon start, which can be very large and hard to follow.

Use --since with a recent time like '10m' or '1h' to limit output to recent events.

Summary

Use 'docker events' to watch Docker actions like container start, stop, image pull, and remove in real time.

Apply --filter flags to focus on specific event types and reduce noise.

Use --since to limit events to a recent time window for easier monitoring.

Practice

1. What does the docker events command do?

easy

A. Displays the Docker container logs

B. Lists all Docker images on the system

C. Shows real-time Docker activity and events

D. Removes unused Docker volumes

Solution

1. Step 1: Understand the purpose of docker events

   This command streams real-time events from the Docker daemon, showing activities like container start, stop, create, etc.

2. Step 2: Compare with other Docker commands

   Other options like listing images, showing logs, or removing volumes do not relate to event monitoring.

3. Final Answer:

   Shows real-time Docker activity and events -> Option C

4. Quick Check:

   docker events = real-time Docker activity [OK]

Hint: Remember: events = live Docker activity stream [OK]

Common Mistakes:

• Confusing events with logs
• Thinking it lists images
• Assuming it cleans resources

2. Which of the following is the correct syntax to monitor Docker events for a specific container with ID abc123?

easy

A. docker logs --events abc123

B. docker events --filter container=abc123

C. docker monitor --container abc123

D. docker events -c abc123

Solution

1. Step 1: Identify the correct filter syntax for docker events

   The correct filter flag is --filter or -f with key=value pairs, e.g., container=abc123.

2. Step 2: Check other options for correctness

   Options A, B, and C use invalid commands or flags not supported by docker events.

3. Final Answer:

   docker events --filter container=abc123 -> Option B

4. Quick Check:

   Use --filter container=ID to monitor specific container events [OK]

Hint: Use --filter container=ID to target container events [OK]

Common Mistakes:

• Using wrong flags like -c
• Confusing docker logs with docker events
• Using non-existent commands like docker monitor

3. What will be the output of the command docker events --filter event=start --filter container=myapp when the container myapp starts?

medium

A. A real-time event line showing the container myapp started

B. A list of all containers currently running

C. An error saying invalid filter syntax

D. No output until the container stops

Solution

1. Step 1: Understand the filters used

   The command filters events to show only start events for the container named myapp.

2. Step 2: Predict output when container starts

   When myapp starts, the command outputs a line describing this event in real-time.

3. Final Answer:

   A real-time event line showing the container myapp started -> Option A

4. Quick Check:

   Filtered events show matching container start events [OK]

Hint: Filters show only matching events live [OK]

Common Mistakes:

• Expecting a list of containers instead of events
• Thinking filters cause errors
• Assuming output only on container stop

4. You run docker events --filter event=stop --filter container=webapp but see no output when the container webapp stops. What is the most likely cause?

medium

A. The docker daemon is not running

B. Docker events do not capture stop events

C. The command syntax is invalid

D. The container name is incorrect or misspelled

Solution

1. Step 1: Verify container name correctness

   If the container name is wrong, no matching events will appear even if the container stops.

2. Step 2: Check other possibilities

   The docker daemon must be running for events; syntax is correct; stop events are captured by docker events.

3. Final Answer:

   The container name is incorrect or misspelled -> Option D

4. Quick Check:

   Correct container name needed for event filtering [OK]

Hint: Check container name spelling when no events appear [OK]

Common Mistakes:

• Assuming docker events miss stop events
• Ignoring daemon status
• Thinking syntax is wrong without checking name

5. You want to monitor Docker events for containers with label env=production and only see start and die events. Which command achieves this?

hard

A. docker events --filter label=env=production --filter event=start --filter event=die

B. docker events --filter label=env=production --filter event=start,die

C. docker events --filter label=env=production --filter event=start --filter event=stop

D. docker events --filter env=production --filter event=start --filter event=die

Solution

1. Step 1: Use multiple --filter flags for each event

   Docker events supports multiple filters; to filter multiple events, repeat the --filter event= flag for each event.

2. Step 2: Use correct label filter syntax

   The label filter requires label=key=value format, so label=env=production is correct.

3. Step 3: Eliminate incorrect options

   docker events --filter label=env=production --filter event=start,die uses comma-separated events which is invalid; docker events --filter label=env=production --filter event=start --filter event=stop uses stop instead of die; docker events --filter env=production --filter event=start --filter event=die uses incorrect label filter syntax.

4. Final Answer:

   docker events --filter label=env=production --filter event=start --filter event=die -> Option A

5. Quick Check:

   Multiple --filter flags for each event and correct label syntax [OK]

Hint: Repeat --filter for each event; label filter needs key=value [OK]

Common Mistakes:

• Using comma-separated events in one filter
• Wrong label filter syntax
• Confusing event names like die vs stop