Docker exec into stopped container | Resolved

Wondering how to resolve Docker exec into stopped container? you are in luck! Our experts have put together this guide to help you get started. Our Docker Support team is here to lend a hand with your queries and issues.

Docker exec into stopped container

Basically, the 

execCopy Code

 command, which allows you to execute a command inside of a running Docker container.

This works excellent and will enable us to dive into a running container to inspect certain things like files in the file system, running processes, and other stuff.

However, 

execCopy Code

 does not work when the Docker container stopped already. T

Today, let us see how our support techs demonstrate how to run commands in stopped Docker containers.

When we try to run 

/bin/shCopy Code

 on a stopped container using 

docker execCopy Code

, Docker will throw a 

No such containerCopy Code

 error.

We have to transform the stopped Docker container into a new Docker image before we can inspect the internals of the container.

We can transform a container into a Docker image using the 

commitCopy Code

 command.

All we need to know is the name or the identifier of the stopped container. (You can get a list of all stopped containers with 

docker ps -aCopy Code

).

docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS NAMES
0dfd54557799 ubuntu “/bin/bash” 25 seconds ago Exited (1) 4 seconds ago peaceful_feynman

Having the identifier 

0dfd54557799Copy Code

 of the stopped container, we can create a new Docker image.

The resulting image will have the same state as the previously stopped container.

At this point, we use 

docker runCopy Code

 and overwrite the original 

entrypointCopy Code

 to get a way into the container.

# Commit the stopped image
docker commit 0dfd54557799 debug/ubuntu

# now we have a new image
docker images list
REPOSITORY TAG IMAGE ID CREATED SIZE
debug/ubuntu <none> cc9db32dcc2d 2 seconds ago 64.3MB

# create a new container from the “broken” image
docker run -it –rm –entrypoint sh debug/ubuntu
# inside of the container we can inspect – for example, the file system
$ ls /app
App.dll
App.pdb
App.deps.json
# CTRL+D to exit the container

# delete the container and the image
docker image rm debug/ubuntu

Conclusion

To conclude, our Support Engineers demonstrated the cause behind the Docker exec into stopped container error and how to resolve it easily.