Opening a shell in container in Docker - Mini Project: Build & Apply

Opening a Shell in a Docker Container

📖 Scenario: You are working with Docker containers to run applications. Sometimes, you need to open a shell inside a running container to check files, run commands, or debug issues.

🎯 Goal: Learn how to open an interactive shell inside a running Docker container using the correct Docker command.

📋 What You'll Learn

Use the exact container name my_container

Use the docker exec command to open a shell

Use /bin/bash as the shell to open

💡 Why This Matters

🌍 Real World

Opening a shell inside a Docker container helps developers and system administrators inspect and debug running applications easily.

💼 Career

Knowing how to interact with containers is essential for DevOps roles, cloud engineers, and developers working with containerized applications.

1

Identify the running container

Create a variable called container_name and set it to the string "my_container".

Docker

# Create a variable called container_name with value "my_container"
# Your code here

Hint

Use quotes around the container name string.

2

Prepare the Docker exec command

Create a variable called shell_command and set it to the string "/bin/bash".

Docker

container_name = "my_container"
# Create a variable called shell_command with value "/bin/bash"
# Your code here

Hint

Use quotes around the shell path string.

3

Construct the full Docker exec command

Create a variable called docker_exec_command that uses an f-string to combine docker exec -it, the container_name, and the shell_command. The command should look like docker exec -it my_container /bin/bash.

Docker

container_name = "my_container"
shell_command = "/bin/bash"
# Create docker_exec_command using f-string to combine 'docker exec -it', container_name, and shell_command
# Your code here

Hint

Use an f-string with curly braces around variable names.

4

Print the Docker exec command

Write a print statement to display the value of docker_exec_command.

Docker

container_name = "my_container"
shell_command = "/bin/bash"
docker_exec_command = f"docker exec -it {container_name} {shell_command}"
# Print the docker_exec_command variable
# Your code here

Hint

Use print(docker_exec_command) to show the command.

Practice

1. What is the main purpose of the command docker exec -it <container> /bin/bash?

easy

A. To stop a running container

B. To start a new container from an image

C. To open an interactive shell inside a running container

D. To build a Docker image

Solution

1. Step 1: Understand the command components

   The command uses docker exec to run a command inside a running container. The -it flags make the session interactive and allocate a terminal.

2. Step 2: Identify the command's effect

   Using /bin/bash opens a shell inside the container, allowing direct interaction.

3. Final Answer:

   To open an interactive shell inside a running container -> Option C

4. Quick Check:

   docker exec -it container /bin/bash = open shell [OK]

Hint: Remember exec + -it + shell opens container shell [OK]

Common Mistakes:

• Confusing exec with docker run
• Forgetting the -it flags for interactivity
• Trying to open shell in a stopped container

2. Which of the following is the correct syntax to open a shell inside a running Docker container named webapp?

easy

A. docker exec -it webapp /bin/sh

B. docker start -it webapp /bin/sh

C. docker run -it webapp /bin/sh

D. docker exec webapp -it /bin/sh

Solution

1. Step 1: Recall the correct order of docker exec flags

   The -it flags must come immediately after docker exec and before the container name.

2. Step 2: Check the command structure

   The correct syntax is docker exec -it <container> <shell>. docker exec -it webapp /bin/sh matches this exactly.

3. Final Answer:

   docker exec -it webapp /bin/sh -> Option A

4. Quick Check:

   Flags -it come before container name [OK]

Hint: Flags -it always come right after exec command [OK]

Common Mistakes:

• Placing -it after container name
• Using docker run instead of exec
• Using docker start with shell command

3. Given a running container named db, what will be the output of the command docker exec -it db /bin/false?

medium

A. The command exits immediately with no shell opened

B. Error: container not found

C. An interactive shell opens inside the container

D. The container stops running

Solution

1. Step 1: Understand the command /bin/false

   The command /bin/false is a program that immediately exits with a failure status and does not open a shell.

2. Step 2: Predict the command behavior inside the container

   Running docker exec -it db /bin/false will run /bin/false inside the container, which exits immediately without opening a shell.

3. Final Answer:

   The command exits immediately with no shell opened -> Option A

4. Quick Check:

   /bin/false exits immediately, no shell [OK]

Hint: Commands like /bin/false exit immediately, no shell [OK]

Common Mistakes:

• Expecting a shell to open
• Confusing container not found error
• Thinking container stops after exec

4. You try to open a shell inside a running container with docker exec -it mycontainer /bin/bash but get the error: OCI runtime exec failed: exec failed: container_linux.go:xxx: exec: "/bin/bash": stat /bin/bash: no such file or directory. What is the best way to fix this?

medium

A. Restart the Docker daemon

B. Use /bin/sh instead of /bin/bash

C. Rebuild the container image

D. Stop and remove the container

Solution

1. Step 1: Analyze the error message

   The error says /bin/bash does not exist inside the container, so the shell is missing.

2. Step 2: Choose an alternative shell

   Many containers have /bin/sh instead of /bin/bash. Using /bin/sh usually works.

3. Final Answer:

   Use /bin/sh instead of /bin/bash -> Option B

4. Quick Check:

   Use available shell like /bin/sh if /bin/bash missing [OK]

Hint: Try /bin/sh if /bin/bash not found inside container [OK]

Common Mistakes:

• Restarting Docker daemon unnecessarily
• Rebuilding image without checking shell availability
• Removing container without trying alternative shells

5. You want to open a shell inside a running container named app but it does not have /bin/bash or /bin/sh. Which command can you try to open a shell if ash is installed inside the container?

hard

A. docker exec -it app /bin/zsh

B. docker exec -it app /bin/bash

C. docker exec -it app /bin/sh

D. docker exec -it app /bin/ash

Solution

1. Step 1: Identify available shells inside container

   If /bin/bash and /bin/sh are missing, but ash is installed, you can use /bin/ash to open a shell.

2. Step 2: Use docker exec with the correct shell path

   The command docker exec -it app /bin/ash opens an interactive shell using ash inside the container.

3. Final Answer:

   docker exec -it app /bin/ash -> Option D

4. Quick Check:

   Use shell installed inside container, e.g. /bin/ash [OK]

Hint: Try shells like /bin/ash if bash and sh missing [OK]

Common Mistakes:

• Assuming bash or sh always exist
• Using wrong shell path
• Not checking installed shells inside container