Why Listing containers (docker ps, docker ps -a)? - Purpose & Use Cases

The Big Idea

What if you could instantly see all your containers' status without opening each one?

The Scenario

Imagine you have many boxes (containers) in your room, but you don't know which ones are open or closed. You try to remember or open each box one by one to see what's inside.

The Problem

This manual checking is slow and confusing. You might forget which boxes you already checked or miss some. It's easy to make mistakes and waste time.

The Solution

Using docker ps commands is like having a list that shows all your boxes and their status at a glance. You can quickly see which containers are running or stopped without opening each one.

Before vs After

✗ Before

Look inside each container folder manually to check status

✓ After

docker ps  # shows running containers
docker ps -a  # shows all containers including stopped ones

What It Enables

This lets you manage and monitor your containers easily, saving time and avoiding confusion.

Real Life Example

A developer wants to see which apps are currently running on their computer and which ones stopped earlier. They run docker ps to get a quick list instead of guessing or checking one by one.

Key Takeaways

Manually checking containers is slow and error-prone.

docker ps commands give a clear, quick list of containers.

This helps you manage containers efficiently and avoid mistakes.

Practice

1. What does the command docker ps show by default?

easy

A. Only running containers

B. All containers, running and stopped

C. Only stopped containers

D. Docker images available locally

Solution

1. Step 1: Understand the default behavior of docker ps

   The docker ps command lists containers that are currently running.

2. Step 2: Compare with other options

   To see all containers, including stopped ones, you use docker ps -a. The command does not list images.

3. Final Answer:

   Only running containers -> Option A

4. Quick Check:

   docker ps = running containers [OK]

Hint: Remember: docker ps shows running containers only [OK]

Common Mistakes:

• Thinking docker ps shows all containers
• Confusing containers with images
• Assuming stopped containers show without -a

2. Which of the following commands correctly lists all containers, including stopped ones?

easy

A. docker ps --stopped

B. docker ps

C. docker ps --running

D. docker ps -a

Solution

1. Step 1: Identify the flag for listing all containers

   The -a flag with docker ps lists all containers, running or stopped.

2. Step 2: Check other options

   docker ps alone shows only running containers. The options --running and --stopped are invalid flags.

3. Final Answer:

   docker ps -a -> Option D

4. Quick Check:

   docker ps -a = all containers [OK]

Hint: Use -a to list all containers, not just running [OK]

Common Mistakes:

• Using docker ps without -a to see stopped containers
• Trying invalid flags like --running
• Confusing container listing with image listing

3. Given the following output from docker ps -a:

CONTAINER ID   IMAGE     STATUS              NAMES
abc123        nginx     Up 2 hours          webserver
def456        redis     Exited (0) 3 days ago cache

What will docker ps show?

medium

A. Both containers: webserver and cache

B. Only the cache container

C. Only the webserver container

D. No containers

Solution

1. Step 1: Analyze the status of containers

   The container named webserver is "Up 2 hours" meaning it is running. The container named cache is "Exited", meaning it is stopped.

2. Step 2: Understand docker ps output

   docker ps shows only running containers, so it will list only webserver.

3. Final Answer:

   Only the webserver container -> Option C

4. Quick Check:

   Running containers = webserver only [OK]

Hint: Check STATUS: 'Up' means running, 'Exited' means stopped [OK]

Common Mistakes:

• Listing stopped containers with docker ps
• Assuming all containers show without -a
• Confusing container names with images

4. You run docker ps -a but get an error: unknown flag: --all. What is the likely cause?

medium

A. You typed --all instead of -a

B. Docker daemon is not running

C. You need to run the command as root

D. The container list is empty

Solution

1. Step 1: Check the flag syntax

   The correct flag to list all containers is -a, not --all. The error shows the flag is unknown.

2. Step 2: Rule out other causes

   If the daemon was not running, the error would be different. Running as root is not required for listing containers. An empty list does not cause a flag error.

3. Final Answer:

   You typed --all instead of -a -> Option A

4. Quick Check:

   Use -a flag, not --all [OK]

Hint: Use short flag -a, not --all [OK]

Common Mistakes:

• Using invalid flag --all
• Assuming root is needed for listing
• Ignoring daemon status errors

5. You want to list all containers but only see their IDs and names, not other details. Which command achieves this?

hard

A. docker ps -a --short

B. docker ps -a --format "{{.ID}} {{.Names}}"

C. docker ps -a --quiet

D. docker ps --filter id --filter name

Solution

1. Step 1: Understand formatting options

   The --format flag lets you customize output. Using {{.ID}} {{.Names}} shows only container IDs and names.

2. Step 2: Evaluate other options

   --quiet shows only IDs, not names. --filter is for filtering, not formatting. --short is not a valid flag.

3. Final Answer:

   docker ps -a --format "{{.ID}} {{.Names}}" -> Option B

4. Quick Check:

   Use --format to customize output [OK]

Hint: Use --format to show only needed fields [OK]

Common Mistakes:

• Using invalid flags like --short
• Confusing --quiet with showing names
• Trying to filter instead of format output