Solution:Step 1: Check fluentd-addressThe address uses a hostname 'fluentd-server' which must be resolvable.Step 2: DNS resolutionIf the Docker host cannot resolve this hostname, logs won't reach Fluentd.Final Answer:The hostname 'fluentd-server' cannot be resolved by the Docker host -> Option BQuic

[Solved] You run:docker run --log-driver=fluentd --log-opt fluentd-address=fluentd-server:24224 myappbut no logs appear in Fluentd. What is the most probable cause? | Docker

Docker - Logging and Monitoring

You run:

docker run --log-driver=fluentd --log-opt fluentd-address=fluentd-server:24224 myapp

but no logs appear in Fluentd. What is the most probable cause?

AThe container image 'myapp' does not generate logs

BThe hostname 'fluentd-server' cannot be resolved by the Docker host

CThe Docker daemon does not support the fluentd log driver

DFluentd requires logs to be sent over UDP, not TCP

Step-by-Step Solution

Solution:

Step 1: Check fluentd-address
The address uses a hostname 'fluentd-server' which must be resolvable.
Step 2: DNS resolution
If the Docker host cannot resolve this hostname, logs won't reach Fluentd.
Final Answer:
The hostname 'fluentd-server' cannot be resolved by the Docker host -> Option B
Quick Check:
Verify hostname resolution from Docker host [OK]

Quick Trick: Hostname resolution failure blocks log forwarding [OK]

Common Mistakes:

Assuming image log generation is the issue
Ignoring DNS resolution problems
Misunderstanding Fluentd transport protocols

Master "Logging and Monitoring" in Docker

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Docker Quizzes

You run:

Step 1: Check fluentd-address

Step 2: DNS resolution

Final Answer:

Quick Check:

Want More Practice?