How to stop a running Docker container?

Stopping a Running Docker Container

As a Docker expert, I'm happy to help you understand how to stop a running Docker container. This is a common task that every Docker user should be familiar with, as it allows you to gracefully terminate a container when it's no longer needed or when you need to make changes to the container's configuration.

Stopping a Container Using the docker stop Command

The most straightforward way to stop a running Docker container is to use the docker stop command. This command sends a SIGTERM signal to the container's primary process, giving it a chance to gracefully shut down. If the container doesn't stop within a specified timeout (default is 10 seconds), the docker stop command will send a SIGKILL signal to forcefully terminate the container.

Here's the basic syntax for the docker stop command:

docker stop [OPTIONS] CONTAINER [CONTAINER...]

To stop a single container, you can simply run:

docker stop my-container

If you have multiple containers running and want to stop them all, you can provide a space-separated list of container names or IDs:

docker stop container1 container2 container3

You can also use the container's ID instead of the name:

docker stop 1a2b3c4d5e6f

Stopping a Container Using the docker kill Command

If you need to stop a container immediately, without giving it a chance to gracefully shut down, you can use the docker kill command. This command sends a SIGKILL signal to the container's primary process, which forcefully terminates the container.

Here's the basic syntax for the docker kill command:

docker kill [OPTIONS] CONTAINER [CONTAINER...]

To stop a single container using docker kill, you can run:

docker kill my-container

And to stop multiple containers, you can use a space-separated list of container names or IDs:

docker kill container1 container2 container3

Understanding the Difference Between docker stop and docker kill

The main difference between docker stop and docker kill is the way they terminate the container's primary process:

• docker stop sends a SIGTERM signal, giving the container a chance to gracefully shut down. This is the preferred method for stopping containers, as it allows the container's processes to perform any necessary cleanup or shutdown tasks.
• docker kill sends a SIGKILL signal, which forcefully terminates the container's primary process without giving it a chance to shut down gracefully. This should be used only when the container is not responding to the SIGTERM signal or when you need to stop the container immediately.

In general, it's best to use docker stop to stop your containers, as it allows for a more controlled and graceful shutdown. However, in certain situations, such as when a container is stuck or unresponsive, docker kill may be necessary to force the container to stop.

Visualizing the Stopping Process

Here's a Mermaid diagram that illustrates the process of stopping a Docker container using the docker stop and docker kill commands:

This diagram shows that when you run docker stop, the container receives a SIGTERM signal, allowing it to gracefully shut down. If the container doesn't stop within the specified timeout, docker stop will then send a SIGKILL signal to forcefully terminate the container. In contrast, docker kill immediately sends a SIGKILL signal, which forcefully terminates the container without giving it a chance to shut down gracefully.

I hope this explanation helps you understand how to stop a running Docker container. Let me know if you have any further questions!