Inspecting container details in Docker - Step-by-Step Execution

Process Flow - Inspecting container details

Start: Have running container

↓

Run 'docker ps' to list containers

↓

Choose container ID or name

↓

Run 'docker inspect <container>'

↓

View detailed JSON info about container

↓

Use info for debugging or monitoring

This flow shows how to list running containers, pick one, and inspect its detailed information using Docker commands.

Execution Sample

Docker

docker ps
# Lists running containers

docker inspect my_container
# Shows detailed info about 'my_container'

Lists running containers and then inspects details of a chosen container.

Process Table

Step	Command Run	Action	Output Summary
1	docker ps	List running containers	Shows container IDs, names, status, ports
2	docker inspect my_container	Get detailed info	Outputs JSON with config, state, network, mounts
3	Parse JSON output	Read container details	See IP address, volumes, environment variables
4	Use info for troubleshooting	Apply knowledge	Fix issues or monitor container health
5	End	No further commands	Inspection complete

💡 Inspection ends after detailed container info is retrieved and reviewed

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
container_list	empty	list of running containers	unchanged	unchanged	unchanged
selected_container	none	none	my_container	my_container	my_container
container_details	none	none	raw JSON data	parsed JSON data	parsed JSON data

Key Moments - 3 Insights

Why do we run 'docker ps' before 'docker inspect'?

Because 'docker ps' shows which containers are running and their IDs or names, so you know what to inspect. See execution_table step 1 and 2.

What kind of information does 'docker inspect' provide?

'docker inspect' outputs detailed JSON including container config, network settings, and state. This is shown in execution_table step 2 and 3.

Can you inspect a container that is not running?

Yes, 'docker inspect' works on any container by ID or name, running or stopped. But 'docker ps' only lists running containers, so you might need 'docker ps -a' to see all.

Visual Quiz - 3 Questions

Look at the execution table, what command lists running containers?

A docker inspect my_container

B docker run

C docker ps

D docker stop

💡 Hint

Check execution_table row 1 under 'Command Run'

At which step do we get the detailed JSON info about the container?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at execution_table row 2 'Action' and 'Output Summary'

If you want to inspect a stopped container, what should you do differently?

A Use 'docker ps' as usual

B Use 'docker ps -a' to list all containers

C Restart the container first

D You cannot inspect stopped containers

💡 Hint

Refer to key_moments about inspecting stopped containers

Concept Snapshot

docker ps
# Lists running containers

docker inspect <container>
# Shows detailed JSON info about the container

Use 'docker ps -a' to see all containers including stopped ones

Inspect output helps debug and monitor container state

Full Transcript

To inspect container details, first list running containers with 'docker ps'. This shows container IDs and names. Then choose a container and run 'docker inspect <container>' to get detailed JSON info about its configuration, state, network, and mounts. This info helps you understand the container's environment and troubleshoot issues. You can inspect stopped containers by listing all containers with 'docker ps -a'.