Opening a shell in container in Docker - Commands & Configuration

Introduction

Sometimes you need to look inside a running container to check files, run commands, or debug problems. Opening a shell inside the container lets you do this easily.

When you want to check the contents of files inside a running container.

When you need to run commands manually inside the container for debugging.

When you want to inspect environment variables or running processes inside the container.

When you want to test changes inside the container before updating the image.

When you want to troubleshoot why an application inside the container is not working.

Commands

This command lists all running containers so you can find the container ID or name to open a shell inside.

Terminal

docker ps

Expected Output

CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS                    NAMES

b7c8f9a1d2e3   nginx:1.23.3   "/docker-entrypoint.…"   2 minutes ago   Up 2 minutes   0.0.0.0:8080->80/tcp     my-nginx

This command opens an interactive shell inside the running container named 'my-nginx'. The '-it' flags allow you to interact with the shell.

Terminal

docker exec -it my-nginx /bin/sh

Expected Output

# 

→

-i - Keep STDIN open so you can type commands

→

-t - Allocate a pseudo-TTY so the shell works interactively

This command exits the shell inside the container and returns you to your host terminal.

Terminal

exit

Expected Output

No output (command runs silently)

Key Concept

If you remember nothing else from this pattern, remember: use 'docker exec -it <container_name> /bin/sh' to open an interactive shell inside a running container.

Common Mistakes

Trying to open a shell in a container that is not running.

The 'docker exec' command only works on running containers, so it will fail if the container is stopped.

First run 'docker ps' to confirm the container is running, or start it with 'docker start <container_name>' before opening a shell.

Using '/bin/bash' in containers that only have '/bin/sh'.

Some lightweight containers like 'nginx' do not have bash installed, so the shell command fails.

Use '/bin/sh' which is more commonly available in minimal containers.

Omitting the '-it' flags when running 'docker exec'.

Without '-it', the shell is not interactive and you cannot type commands inside the container.

Always include '-it' to open an interactive terminal session.

Summary

Use 'docker ps' to find the running container's name or ID.

Run 'docker exec -it <container_name> /bin/sh' to open an interactive shell inside the container.

Type 'exit' to leave the container shell and return to your host terminal.

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