Viewing container logs in Docker - Step-by-Step Execution

Process Flow - Viewing container logs

Start Docker Container

↓

Container Runs

↓

Logs Generated

↓

Run 'docker logs <container>'

↓

Docker Fetches Logs

↓

Display Logs to User

↓

User Reads Logs or Follows with -f

↓

End or Continue Following

This flow shows how logs are generated by a running container and how the 'docker logs' command fetches and displays them to the user.

Execution Sample

Docker

docker run -d --name myapp nginx

docker logs myapp

docker logs -f myapp

Starts an nginx container in the background, then shows how to view its logs and follow live log output.

Process Table

Step	Command Run	Action	Result/Output
1	docker run -d --name myapp nginx	Start container named 'myapp' in detached mode	Container ID printed, nginx starts running
2	docker logs myapp	Fetch logs from 'myapp' container	Shows nginx startup logs (e.g., 'Starting nginx...')
3	docker logs -f myapp	Follow logs live from 'myapp'	Shows current logs and waits, streaming new logs as they appear
4	Ctrl+C to stop following	Stop live log streaming	Returns to command prompt

💡 User stops following logs or container stops running

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Container State	Not running	Running (nginx started)	Running (logs fetched)	Running (logs streaming)	Running or stopped depending on user
Logs Available	None	Startup logs generated	Logs displayed once	Logs displayed continuously	Logs remain stored until container removed

Key Moments - 2 Insights

Why do we use '-f' with 'docker logs'?

Using '-f' streams logs live as they are generated, shown in execution_table step 3, so you can watch events in real time instead of seeing only past logs.

What happens if the container is not running when we run 'docker logs'?

You still get the logs generated before the container stopped, because logs are stored until container removal. This is implied in variable_tracker where logs remain available after container stops.

Visual Quiz - 3 Questions

Look at the execution table, what does the command in step 2 do?

A Starts the container named 'myapp'

B Fetches and displays logs from the 'myapp' container

C Stops the container named 'myapp'

D Removes the container named 'myapp'

💡 Hint

Refer to the 'Action' and 'Result/Output' columns in step 2 of the execution table

At which step does the user start seeing live log updates?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Check the 'Action' column for 'Follow logs live' in the execution table

If the container stops running, what happens to the logs when you run 'docker logs'?

A Logs are lost and cannot be retrieved

B Logs are still available and displayed

C Docker restarts the container automatically

D You get an error saying container not found

💡 Hint

See variable_tracker row 'Logs Available' after container stops

Concept Snapshot

docker logs <container>
- Shows logs from a container
- Use -f to follow logs live
- Logs persist after container stops
- Useful for debugging running or stopped containers

Full Transcript

This lesson shows how to view logs from a Docker container. First, you start a container in detached mode. The container runs and generates logs. You can fetch these logs anytime using 'docker logs <container>'. Adding '-f' streams logs live as they are created. Logs remain available even if the container stops, until it is removed. This helps you monitor and debug containers easily.