Скачать или смотреть How to Troubleshoot Docker Container Launch Issues with Ubuntu Images

Struggling with Docker containers not starting from Ubuntu images? Discover the common pitfalls and solutions for a successful container startup in this comprehensive guide.
---
This video is based on the question https://stackoverflow.com/q/64627928/ asked by the user 'GTRekter' ( https://stackoverflow.com/u/6613232/ ) and on the answer https://stackoverflow.com/a/64628550/ provided by the user 'rzlvmp' ( https://stackoverflow.com/u/13946204/ ) 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 not starting with ubuntu image (docker start)

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 Container Startup Issues with Ubuntu Images

If you're encountering issues with your Docker containers not starting when using Ubuntu images, you’re not alone. Many developers face dilemmas when trying to keep their containers alive after exiting a session. This guide will delve into the core of the problem and equip you with the knowledge to successfully manage your Docker containers.

Understanding the Problem

When you run a container from an Ubuntu image using the command docker container run ubuntu, everything appears to be running smoothly at first. However, upon exiting the pseudo-terminal, the process seems to disappear, and you can’t restart the container as expected.

The root concern lies in the way the command is initiated and how Docker manages the container's lifecycle. When using the command docker run <IMAGE ID>, if the command inside the container is not running in a persistent state, the container exits immediately once you exit the terminal or command-line interface.

Why Does the Container Stop Running?

The primary reason your container stops running is due to the nature of the entry command you've provided to Docker. Let's dissect how Docker manages commands and containers:

Docker containers live as long as the command running inside is still active.

In this case, you’re using "/bin/bash" as the command to start, which initiates a shell session.

Pseudo-TTY Explanation

When using "/bin/bash" without any additional flags, you're starting a session that requires interaction (known as a pseudo-terminal). When you exit this terminal, the session ends, and consequently, the Docker container stops as there’s no longer a process running inside it.

Solutions to Keep Your Container Running

To resolve this, you can use specific flags when running your Docker container to ensure it remains active even after closing the terminal.

1. Running with the -it Flags

If you want the container to run interactively, you’ll need to use the -it option, which stands for:

-i: Keep STDIN open even if not attached.

-t: Allocate a pseudo-TTY.

You would run your container like this:

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

This way, the container remains open for interaction, and it will not exit until you explicitly terminate the session.

2. Running Commands without Interactivity

If your intention is to run a command without waiting for user input, consider the following:

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

This command demonstrates that the container runs a simple command (echo 'Hello World') and exits right afterward. In this case, since there's no interactive shell, it will not hang or wait for input.

3. Understanding the Flow of Execution

It’s crucial to grasp how the execution flow impacts the container. Here are two scenarios to compare:

When you run docker run ubuntu, it waits for a command in the interactive mode.

When running docker run -it ubuntu, the commands are evaluated in a loop, and the container remains active for input until you decide to close it.

Conclusion

Understanding how Docker manages container life cycles relative to the commands provided is key to resolving issues when your container abruptly stops. The next time you encounter issues starting your container from an Ubuntu image, remember these solutions. Happy Dockering!