Скачать или смотреть Understanding Why Your Docker Container Exits and How to Re-Start It

Learn how to troubleshoot Docker container issues where the container exists but does not run, and understand how to start a stopped container efficiently.
---
This video is based on the question https://stackoverflow.com/q/68586689/ asked by the user 'delalma' ( https://stackoverflow.com/u/8867871/ ) and on the answer https://stackoverflow.com/a/68587112/ provided by the user 'usuario' ( https://stackoverflow.com/u/7502800/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: docker container exist but does not run with container ID

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting Docker Containers: Understanding and Managing Exit Status

Managing Docker containers can sometimes be a bit perplexing, especially when you find yourself in a situation where a container exists but does not run. This article will shed light on a common scenario faced by many Docker users, helping you grasp why it happens and how to solve it effectively.

The Problem: Exiting Containers

Imagine you’ve created a Docker container that works perfectly well at first. However, after some time, you run a command like docker ps -a only to find that your container has exited with a status code of 137. The command output looks something like this:

[[See Video to Reveal this Text or Code Snippet]]

When you try to run the container again with the command:

[[See Video to Reveal this Text or Code Snippet]]

Instead of re-opening the existing container, you create a new one entirely with a different container ID. This leads to confusion and frustration. So, why does this happen?

The Explanation: Docker Run vs. Docker Start

Whenever you execute the command docker run, you are instructing Docker to create a new container from the specified image. In this case, since your original container with ID abc6f4d50931 has exited, executing docker run will not reactivate the existing container. Instead, it will create a new instance, which is why you see a new container ID each time you run it.

Here are some key points to remember:

Running docker run ... always aims to initiate a new container.

The exit status of your container indicates that it has stopped working; in this case, it's marked as "Exited." You can check this status using docker ps -a.

Each time you run with the docker run command, a new container is spun up from the specified image.

The Solution: Starting the Existing Container

To restart the existing container, you should use the docker start command followed by the container ID. In your scenario, this would look like:

[[See Video to Reveal this Text or Code Snippet]]

Steps to Restart Your Container:

Identify the Container ID: Use docker ps -a to locate the ID of the stopped container.

Use the Correct Command: Execute docker start <CONTAINER_ID>, replacing <CONTAINER_ID> with the actual ID of the container you want to run again.

Example:

Here’s how your command should look based on the example above:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Navigating Docker containers efficiently is crucial for optimizing your development workflow. By understanding the difference between docker run and docker start, you can easily manage your containers, bringing existing ones back to life without the hassle of creating new instances unnecessarily. Remember, when you run into a stopped container situation, always opt for docker start to get back to your old friend instead of running docker run, which will spawn a new one!

With this knowledge, you should be well-prepared to tackle any Docker container issues that come your way.