Why interacting with containers matters in Docker - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do we need to interact with running containers?

Which of the following best explains why interacting with running containers is important in DevOps?

A To monitor and debug applications inside containers in real time.

B To permanently change the container image stored in the registry.

C To increase the container size for more storage automatically.

D To convert containers into virtual machines for better performance.

💡 Hint

Think about what you might do if an app inside a container is not working as expected.

Interacting with running containers allows you to check logs, run commands, and fix issues without rebuilding images. This helps in quick debugging and monitoring.

💻 Command Output

intermediate

Output of docker exec command

What will be the output of the following command if the container named webapp is running and has a file /app/version.txt containing 'v1.2.3'?

Docker

docker exec webapp cat /app/version.txt

A v1.2.3

B Error: No such file or directory

C Container webapp not found

D Permission denied

💡 Hint

Consider what docker exec does when running a command inside a container.

The docker exec command runs the given command inside the specified running container. If the file exists, it outputs its content.

🔀 Workflow

advanced

Correct sequence to interact with a container shell

What is the correct order of commands to start a container named db if stopped, then open an interactive shell inside it?

A 1,3,2,4

B 3,1,2,4

C 1,2,3,4

D 3,2,1,4

💡 Hint

Think about checking container status before starting and interacting.

First, check running containers with docker ps. Then start the container if stopped. Next, open an interactive shell. Stopping is optional and last.

❓ Troubleshoot

advanced

Why does docker exec fail with 'No such container'?

You run docker exec myapp ls but get the error 'Error: No such container: myapp'. What is the most likely cause?

A You do not have permission to run docker commands.

B The 'ls' command is not installed inside the container.

C The container named 'myapp' is not running or does not exist.

D Docker daemon is not running on the host machine.

💡 Hint

Consider what the error message says about the container name.

The error means Docker cannot find a running container with the name 'myapp'. The container might be stopped or never created.

✅ Best Practice

expert

Best practice for persistent data when interacting with containers

Which option describes the best practice to keep data safe and persistent when interacting with containers that may be stopped or removed?

A Copy data to a temporary folder inside the container before stopping it.

B Save data inside the container’s writable layer and commit changes to the image.

C Rely on container snapshots to restore data after removal.

D Use Docker volumes or bind mounts to store data outside the container filesystem.

💡 Hint

Think about how container filesystems behave when containers are deleted.

Container filesystems are ephemeral. Using volumes or bind mounts stores data outside containers, ensuring persistence even if containers are removed.

Practice

1. Why is it important to interact with a running Docker container?

easy

A. To check the container's current status and logs

B. To delete the container permanently

C. To create a new Docker image

D. To install Docker on the host machine

Solution

1. Step 1: Understand container interaction purpose

   Interacting with a running container helps monitor its status and troubleshoot issues.

2. Step 2: Identify correct interaction use

   Checking logs and status is a common reason to interact, unlike deleting or installing Docker.

3. Final Answer:

   To check the container's current status and logs -> Option A

4. Quick Check:

   Container interaction = status check [OK]

Hint: Interacting means checking or controlling running containers [OK]

Common Mistakes:

• Confusing interaction with image creation
• Thinking interaction means deleting containers
• Mixing up Docker installation with container interaction

2. Which of the following commands correctly attaches to a running Docker container named webapp?

easy

A. docker start webapp

B. docker run webapp

C. docker attach webapp

D. docker build webapp

Solution

1. Step 1: Identify command to interact with running container

   The docker attach command connects your terminal to a running container.

2. Step 2: Differentiate from other commands

   docker run starts a new container, docker start starts a stopped container, and docker build creates an image.

3. Final Answer:

   docker attach webapp -> Option C

4. Quick Check:

   Attach = connect to running container [OK]

Hint: Attach connects terminal to running container [OK]

Common Mistakes:

• Using 'docker run' to connect to running container
• Confusing 'docker start' with attaching
• Mixing build command with container interaction

3. What will be the output of the command docker logs mycontainer if the container is running a web server that just started successfully?

medium

A. Error: No such container: mycontainer

B. Server started on port 80

C. Container stopped unexpectedly

D. Usage: docker logs [OPTIONS] CONTAINER

Solution

1. Step 1: Understand purpose of docker logs

   This command shows the output logs of the specified container.

2. Step 2: Predict expected log output

   If the container runs a web server that started successfully, logs will show a startup message like 'Server started on port 80'.

3. Final Answer:

   Server started on port 80 -> Option B

4. Quick Check:

   Logs show container output = startup message [OK]

Hint: Logs show what container prints during run [OK]

Common Mistakes:

• Expecting error when container exists
• Confusing usage message with logs
• Assuming container stopped when running

4. You tried to attach to a container using docker attach myapp but got no response. What is the most likely reason?

medium

A. The container is not running

B. You misspelled the command

C. Docker daemon is not installed

D. The container image is missing

Solution

1. Step 1: Understand docker attach requirements

   This command only works if the container is currently running.

2. Step 2: Analyze possible causes for no response

   If the container is stopped, attach will not connect and appear unresponsive.

3. Final Answer:

   The container is not running -> Option A

4. Quick Check:

   Attach needs running container [OK]

Hint: Attach only works on running containers [OK]

Common Mistakes:

• Assuming command typo without checking container state
• Thinking Docker daemon missing causes attach failure
• Confusing image presence with container running

5. You want to interactively debug a container named dbserver that is running but not responding correctly. Which sequence of commands lets you start a new shell session inside it without stopping the container?

hard

A. docker attach dbserver && exit

B. docker stop dbserver && docker run -it dbserver /bin/bash

C. docker build -t debug dbserver

D. docker exec -it dbserver /bin/bash

Solution

1. Step 1: Identify command to open shell in running container

   docker exec -it runs a new interactive shell inside the running container without stopping it.

2. Step 2: Eliminate incorrect options

   Stopping container loses state, attach connects to main process, build creates image not shell.

3. Final Answer:

   docker exec -it dbserver /bin/bash -> Option D

4. Quick Check:

   Exec runs shell inside running container [OK]

Hint: Use exec -it to open shell inside running container [OK]

Common Mistakes:

• Stopping container before debugging loses state
• Using attach instead of exec for shell access
• Confusing build with container interaction