Bobcares

Docker exec into stopped container | Resolved

by | Jan 1, 2023

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 exec 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, exec 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/sh on a stopped container using docker exec, Docker will throw a No such container 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 commit 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 -a).

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 0dfd54557799 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 run and overwrite the original entrypoint 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.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF