In this lesson, you will learn how to stop a container correctly so that your applications can save their progress and close connections before shutting down.
Why Graceful Matters
When you stop a container, you don't want to simply "pull the plug." If an application is busy writing a file to a database or handling a network request, an abrupt shutdown can lead to data corruption or lost information. Instead, we use "graceful termination."
The Signal Process
In the Linux world, processes communicate using signals. When you issue a stop command (like docker stop), the container runtime sends a specific signal called SIGTERM (Signal Terminate) to the main process inside your container (the process with PID 1).
SIGTERM: This is a polite request. It tells the application, "Please finish what you are doing and shut down safely."- The Buffer Period: Docker gives the application a default timeout (usually 10 seconds) to perform its cleanup, such as closing open files, flushing logs, or telling external services that it is going offline.
SIGKILL: If the application doesn't stop within that timeout, Docker sendsSIGKILL(Signal Kill). This is the "hard stop"—the operating system immediately terminates the process, and the application has no chance to save its state.
A Quick Illustration
Imagine a script that processes a list of transactions. If you trigger a docker stop during that process, your application receives the SIGTERM. If written correctly, your code intercepts that signal, stops accepting new transactions, finishes the one currently in progress, and then exits.
# Gracefully stop a container
docker stop my-app-container
If you ever need to stop a container instantly without waiting for the grace period, you can use docker kill. However, this should be a last resort, as it prevents your application from cleaning up after itself. By ensuring your applications are "signal-aware," you ensure that your services remain reliable even when they are being restarted or updated.
Key Takeaway: Graceful termination uses the SIGTERM signal to request a clean shutdown, protecting your data and connections from the abruptness of a hard kill.