Docker logs for troubleshooting - Step-by-Step Execution

Process Flow - Docker logs for troubleshooting

Start Container

↓

Container Runs

↓

Logs Generated

↓

Run 'docker logs <container>'

↓

View Logs Output

↓

Analyze Logs for Errors

↓

Fix Issues or Restart Container

This flow shows how Docker containers generate logs, how to fetch them using the docker logs command, and then analyze those logs to troubleshoot issues.

Execution Sample

Docker

docker run -d --name myapp nginx
sleep 2
docker logs myapp

Starts an nginx container named 'myapp', waits 2 seconds, then fetches and shows its logs.

Process Table

Step	Command	Action	Output/Result
1	docker run -d --name myapp nginx	Start nginx container in background	Container ID printed, container running
2	sleep 2	Wait 2 seconds for container to initialize	No output, pause
3	docker logs myapp	Fetch logs from 'myapp' container	Shows nginx startup logs, e.g. 'nginx started'
4	docker logs myapp --tail 5	Fetch last 5 log lines	Shows last 5 lines of logs
5	docker logs myapp --follow	Stream logs live	Shows logs continuously until stopped
6	docker logs unknown	Try logs on non-existent container	Error: No such container: unknown

💡 Logs fetched or error shown if container does not exist

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
container_status	none	running	running	running	running
logs_output	empty	empty	empty	nginx startup logs	nginx startup logs or error

Key Moments - 3 Insights

Why do we use 'docker logs' after starting a container?

Because the container runs in the background, 'docker logs' lets us see what happened inside it, like startup messages or errors, as shown in step 3 of the execution_table.

What happens if we try to get logs from a container that doesn't exist?

Docker shows an error message 'No such container', as seen in step 6 of the execution_table, indicating the container name is wrong or container is not running.

How can we see logs as they happen in real time?

Using 'docker logs --follow' streams the logs live, shown in step 5, so we can watch new log lines appear continuously.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output of 'docker logs myapp' at step 3?

A Error: No such container

B Shows nginx startup logs

C Container ID printed

D No output

💡 Hint

Check the 'Output/Result' column for step 3 in execution_table

At which step does Docker show an error for a non-existent container?

A Step 6

B Step 4

C Step 2

D Step 1

💡 Hint

Look for 'Error' message in the 'Output/Result' column in execution_table

If we want to see only the last 5 lines of logs, which command should we use?

A docker logs myapp

B docker logs myapp --follow

C docker logs myapp --tail 5

D docker run myapp

💡 Hint

Refer to step 4 in execution_table for the command that fetches last 5 lines

Concept Snapshot

Docker logs let you see what happens inside a container.
Use 'docker logs <container>' to fetch logs.
Add '--tail N' to see last N lines.
Add '--follow' to stream logs live.
Errors appear if container name is wrong.
Logs help find and fix container issues.

Full Transcript

This lesson shows how Docker containers produce logs and how to use the 'docker logs' command to view them. First, you start a container in the background. Then, you run 'docker logs <container>' to see what happened inside, like startup messages. You can limit output with '--tail' or watch logs live with '--follow'. If you ask for logs of a container that doesn't exist, Docker shows an error. These logs are useful to troubleshoot and fix problems inside containers.