Docker inspect for detailed info - Step-by-Step Execution

Process Flow - Docker inspect for detailed info

Run docker inspect <container>

↓

Docker fetches container metadata

↓

Parse JSON output

↓

Display detailed info

↓

User reads container details

Docker inspect runs a command to get detailed JSON info about a container, then shows it for user review.

Execution Sample

Docker

docker inspect my_container

This command fetches detailed JSON info about the container named 'my_container'.

Process Table

Step	Action	Input/Command	Output/Result
1	User runs inspect	docker inspect my_container	Command sent to Docker daemon
2	Docker daemon fetches metadata	Container ID: abc123	Container JSON metadata prepared
3	Docker returns JSON	JSON data	Detailed container info in JSON format
4	User views output	JSON data	Sees container config, network, mounts, state, etc.
5	End	N/A	User has detailed container info

💡 Docker inspect completes after returning full JSON metadata for the container.

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
container_metadata	empty	fetched JSON metadata	returned JSON data	displayed JSON info

Key Moments - 2 Insights

Why does docker inspect output so much information?

Docker inspect returns all metadata about the container as JSON, including config, network, mounts, and state, as shown in step 3 of the execution table.

Is the output human-friendly?

The output is raw JSON, which can be large and complex, so users often use tools like 'jq' to filter it, but the raw output shows all details as in step 4.

Visual Quiz - 3 Questions

Look at the execution table, what is the output after step 3?

A Command sent to Docker daemon

B User views output

C Detailed container info in JSON format

D Container ID

💡 Hint

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

At which step does Docker fetch the container metadata?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look at the 'Action' column in the execution_table to find when metadata is fetched.

If the container name is wrong, what would happen in the execution flow?

A Docker returns an error instead of JSON metadata

B Docker returns empty JSON

C Docker shows partial container info

D Docker inspects a different container

💡 Hint

Think about what happens if Docker cannot find the container to fetch metadata.

Concept Snapshot

docker inspect <container>
Returns detailed JSON info about the container.
Includes config, network, mounts, and state.
Output is raw JSON, useful for debugging.
Use filters like 'jq' to parse output.

Full Transcript

Docker inspect is a command that shows detailed information about a container. When you run 'docker inspect my_container', Docker fetches all metadata about that container and returns it as JSON. This JSON includes configuration details, network settings, mounted volumes, and the container's current state. The output is raw and can be large, so users often filter it with tools like 'jq'. The process starts when the user runs the command, then Docker fetches the data, returns it, and the user reads the detailed info. If the container name is wrong, Docker will return an error instead of JSON data.

Practice

1. What is the primary purpose of the docker inspect command?

easy

A. To start a new Docker container

B. To show detailed information about Docker objects like containers and images

C. To remove unused Docker images

D. To list all running Docker containers

Solution

1. Step 1: Understand the command's function

   docker inspect is used to get detailed JSON data about Docker objects such as containers, images, volumes, and networks.

2. Step 2: Compare with other Docker commands

   Starting containers is done with docker run, removing images with docker rmi, and listing containers with docker ps. None of these show detailed info like docker inspect.

3. Final Answer:

   To show detailed information about Docker objects like containers and images -> Option B

4. Quick Check:

   docker inspect = detailed info [OK]

Hint: Remember: inspect means look closely at details [OK]

Common Mistakes:

• Confusing inspect with commands that start or list containers
• Thinking inspect modifies containers
• Assuming inspect only works for images

2. Which of the following is the correct syntax to inspect a container named myapp?

easy

A. docker inspect myapp

B. docker inspect -n myapp

C. docker inspect --container myapp

D. docker inspect container=myapp

Solution

1. Step 1: Recall the basic syntax of docker inspect

   The command is docker inspect [OPTIONS] NAME|ID. No extra flags are needed to specify container name.

2. Step 2: Evaluate each option

   docker inspect myapp matches the correct syntax. Options B, C, and D use invalid flags or formats not recognized by Docker.

3. Final Answer:

   docker inspect myapp -> Option A

4. Quick Check:

   docker inspect + container name = correct syntax [OK]

Hint: Use just 'docker inspect' plus container name or ID [OK]

Common Mistakes:

• Adding unnecessary flags like -n or --container
• Using equal signs in command arguments
• Confusing inspect syntax with other Docker commands

3. What will be the output of the command docker inspect --format='{{.NetworkSettings.IPAddress}}' mycontainer?

medium

A. An error because the format is incorrect

B. The container's environment variables

C. The container's mounted volumes

D. The IP address assigned to the container named mycontainer

Solution

1. Step 1: Understand the --format option

   The --format flag allows extracting specific fields from the JSON output using Go templates. Here, {{.NetworkSettings.IPAddress}} targets the container's IP address.

2. Step 2: Match the template to the expected output

   This template returns the IP address string of the container named mycontainer. Other options like environment variables or volumes require different template paths.

3. Final Answer:

   The IP address assigned to the container named mycontainer -> Option D

4. Quick Check:

   --format with IPAddress = container IP [OK]

Hint: Use --format with .NetworkSettings.IPAddress for container IP [OK]

Common Mistakes:

• Confusing IPAddress with environment variables
• Using wrong template syntax causing errors
• Expecting full JSON output instead of filtered data

4. You run docker inspect --format='{{.Config.Env}}' mycontainer but get an empty output. What is the most likely reason?

medium

A. The container has no environment variables set

B. The container name is misspelled

C. The format string is missing quotes

D. The Docker daemon is not running

Solution

1. Step 1: Check the format string correctness

   The format string {{.Config.Env}} is valid and properly quoted, so syntax is correct.

2. Step 2: Consider container state and data

   If the container exists and the command runs without error but returns empty, it means no environment variables were set in the container configuration.

3. Final Answer:

   The container has no environment variables set -> Option A

4. Quick Check:

   Empty Env output = no env vars set [OK]

Hint: Empty Env output usually means no env vars set [OK]

Common Mistakes:

• Assuming empty output means syntax error
• Not verifying container name correctness
• Ignoring Docker daemon status errors

5. You want to list all mount points of a container named webapp using docker inspect. Which command will correctly extract this information?

hard

A. docker inspect --format='{{.MountPoints}}' webapp

B. docker inspect --format='{{.Config.Mounts}}' webapp

C. docker inspect --format='{{json .Mounts}}' webapp

D. docker inspect --format='{{.NetworkSettings.Mounts}}' webapp

Solution

1. Step 1: Identify the correct JSON path for mounts

   The .Mounts field contains an array of mount point objects. Using {{json .Mounts}} converts this array to JSON string output.

2. Step 2: Evaluate other options for correctness

   .Config.Mounts and .NetworkSettings.Mounts do not exist. .MountPoints is not a valid field in Docker inspect output.

3. Final Answer:

   docker inspect --format='{{json .Mounts}}' webapp -> Option C

4. Quick Check:

   Use {{json .Mounts}} to get mount points [OK]

Hint: Use {{json .Mounts}} to get mount info in JSON format [OK]

Common Mistakes:

• Using incorrect JSON paths like .Config.Mounts
• Forgetting to use json function for arrays
• Assuming mount info is under NetworkSettings