Get Inside A Running Docker Container

Sometimes you need to look inside a running container.

Maybe you want to check files, inspect environment variables, confirm a process is running, or understand how the container filesystem looks. Docker lets you do this with docker exec.

Start a container

Run an Nginx container in detached mode:

docker run -d --name web nginx

Check that it is running:

docker ps

Now you can enter it.

Use docker exec

Use this command:

docker exec -it web bash

The options mean:

If the image does not include bash, try:

docker exec -it web sh

Small images often include sh instead of bash.

Explore inside the container

Once inside, try:

pwd
ls
whoami
cat /etc/os-release

For Nginx, you can check the default web files:

cd /usr/share/nginx/html
ls
cat index.html

This helps you see that the container has its own filesystem.

Exit the container shell

To leave the shell:

exit

The container keeps running because you only exited the extra shell process, not the main Nginx process.

Check again:

docker ps

Exec vs attach

Beginners sometimes confuse exec and attach.

For inspection and debugging, prefer docker exec.

Do not manually fix production containers

Getting inside a container is useful for learning and debugging. But in real deployments, you should not manually edit containers and treat those edits as permanent.

If a change is needed, update the Dockerfile or application code, build a new image, and run a new container.

Written By: Shiva Srivastava