{"id":48394,"date":"2025-02-08T08:22:00","date_gmt":"2025-02-08T08:22:00","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=48394"},"modified":"2025-07-12T05:38:44","modified_gmt":"2025-07-12T05:38:44","slug":"docker-stop","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/docker-stop\/","title":{"rendered":"Docker commands Guide – docker stop with examples"},"content":{"rendered":"\n

Here\u2019s a complete tutorial<\/strong> on docker stop<\/code>, including its purpose<\/strong>, how to use it<\/strong>, examples<\/strong>, and use cases<\/strong>.<\/p>\n\n\n\n

\n\n\n\n

What is docker stop<\/code>?<\/strong><\/h2>\n\n\n\n

docker stop<\/code> is a Docker command used to gracefully stop a running container<\/strong> by sending the SIGTERM<\/code> signal<\/strong>. This allows the main process inside the container to perform necessary cleanup before shutting down. If the container doesn\u2019t stop within the specified timeout (default is 10 seconds), Docker sends a SIGKILL<\/code> signal<\/strong> to forcefully stop it.<\/p>\n\n\n\n

Key Features:<\/strong><\/p>\n\n\n\n

    \n
  • Stops running containers gracefully<\/strong> (tries to avoid data loss).<\/li>\n\n\n\n
  • Allows you to specify a timeout<\/strong> before forcing the stop.<\/li>\n\n\n\n
  • Can stop multiple containers<\/strong> at once.<\/li>\n\n\n\n
  • Useful for service management, maintenance, and resource control<\/strong>.<\/li>\n<\/ul>\n\n\n\n
    \n\n\n\n

    Basic Syntax<\/strong><\/h2>\n\n\n
    docker<\/span> stop<\/span> [OPTIONS]<\/span> CONTAINER<\/span> [CONTAINER...]<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    Common Options:<\/strong><\/h3>\n\n\n\n
      \n
    • -t<\/code>, --time<\/code>: Specify the timeout<\/strong> (in seconds) before forcefully stopping the container. The default is 10 seconds.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n
      Examples of docker stop<\/code><\/strong><\/h2>\n\n\n\n
      1. Stop a Running Container<\/strong><\/h3>\n\n\n
      docker stop my_container\n<\/code><\/span><\/pre>\n\n\n
      This sends a SIGTERM<\/code> to the container named my_container<\/code> and waits up to 10 seconds before forcefully stopping it.<\/p>\n\n\n\n
      \n\n\n\n
      2. Stop a Container by ID<\/strong><\/h3>\n\n\n
      docker stop a1b2c3d4e5f6\n<\/code><\/span><\/pre>\n\n\n
      You can stop a container using its unique container ID.<\/p>\n\n\n\n
      \n\n\n\n
      3. Stop Multiple Containers<\/strong><\/h3>\n\n\n
      docker stop container1 container2 container3\n<\/code><\/span><\/pre>\n\n\n
      This command stops multiple containers simultaneously.<\/p>\n\n\n\n
      \n\n\n\n
      4. Stop All Running Containers<\/strong><\/h3>\n\n\n
      docker stop $(docker ps -q)\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This stops all currently running containers.<\/p>\n\n\n\n
      \n\n\n\n
      5. Specify a Custom Timeout<\/strong><\/h3>\n\n\n
      docker stop -t 20 my_container\n<\/code><\/span><\/pre>\n\n\n
      This gives the container 20 seconds to stop gracefully before sending SIGKILL<\/code>.<\/p>\n\n\n\n
      \n\n\n\n
      6. Use in a Shell Script<\/strong><\/h3>\n\n\n
      #!\/bin\/bash<\/span>\ndocker stop web_container db_container cache_container\necho<\/span> \"Containers stopped successfully.\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This script stops specific containers and prints a success message.<\/p>\n\n\n\n
      \n\n\n\n
      7. Stop the Last Created Container<\/strong><\/h3>\n\n\n
      docker stop $(docker ps -lq)\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This stops the most recently created container.<\/p>\n\n\n\n
      \n\n\n\n
      8. Stop Containers with Specific Filters<\/strong><\/h3>\n\n\n\n
      Stop all containers that were created from a specific image:<\/p>\n\n\n
      docker ps -q --filter \"ancestor=nginx\"<\/span> | xargs docker stop\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n\n\n\n
      9. Monitor and Stop Non-Responsive Containers<\/strong><\/h3>\n\n\n
      docker inspect --format='{{.State.Status}}'<\/span> my_container\ndocker stop my_container\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Check the container status before stopping it.<\/p>\n\n\n\n
      \n\n\n\n
      10. Automate Maintenance with docker stop<\/code><\/strong><\/h3>\n\n\n
      #!\/bin\/bash<\/span>\nfor<\/span> container in<\/span> $(docker ps -q); do<\/span>\n  docker stop $container\ndone\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This script stops all running containers one by one.<\/p>\n\n\n\n
      \n\n\n\n
      Use Cases for docker stop<\/code><\/strong><\/h2>\n\n\n\n
      1. Graceful Service Shutdown<\/strong><\/h3>\n\n\n\n
        \n
      • Safely stop services to apply updates<\/strong> or perform maintenance<\/strong>.<\/li>\n\n\n\n
      • Ensure that services have time to clean up resources or write data before shutting down.<\/li>\n<\/ul>\n\n\n\n
        2. Resource Management<\/strong><\/h3>\n\n\n\n
          \n
        • Free up system resources by stopping non-critical containers during high-demand periods.<\/li>\n<\/ul>\n\n\n\n
          3. Debugging and Troubleshooting<\/strong><\/h3>\n\n\n\n
            \n
          • Stop unresponsive or malfunctioning containers for investigation.<\/li>\n\n\n\n
          • Combine with docker logs<\/code> and docker inspect<\/code> to identify issues.<\/li>\n<\/ul>\n\n\n\n
            4. Scheduled Maintenance<\/strong><\/h3>\n\n\n\n
              \n
            • Use docker stop<\/code> in scheduled scripts<\/strong> to stop services during off-peak hours.<\/li>\n<\/ul>\n\n\n\n
              5. CI\/CD Pipelines<\/strong><\/h3>\n\n\n\n
                \n
              • Stop containers after automated tests to ensure a clean environment for the next test cycle.<\/li>\n<\/ul>\n\n\n\n
                6. Cleanup and Recovery<\/strong><\/h3>\n\n\n\n
                  \n
                • Stop and restart containers during service recovery or when replacing outdated services.<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n
                  List of Common docker stop<\/code> Commands<\/strong><\/h2>\n\n\n\n
                  Command<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
                  docker stop my_container<\/code><\/td>Gracefully stop a running container<\/td><\/tr>
                  docker stop container1 container2<\/code><\/td>Stop multiple containers<\/td><\/tr>
                  docker stop a1b2c3d4e5f6<\/code><\/td>Stop a container using its ID<\/td><\/tr>
                  docker stop $(docker ps -q)<\/code><\/td>Stop all running containers<\/td><\/tr>
                  docker stop -t 20 my_container<\/code><\/td>Stop a container with a 20-second timeout<\/td><\/tr>
                  docker stop $(docker ps -lq)<\/code><\/td>Stop the last created container<\/td><\/tr>
                  `docker ps -q –filter “ancestor=nginx”<\/td>xargs docker stop`<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  \n\n\n\n
                  Best Practices for Using docker stop<\/code>:<\/strong><\/h2>\n\n\n\n
                    \n
                  1. Use a reasonable timeout<\/strong> (-t<\/code>) to allow services to shut down cleanly.<\/li>\n\n\n\n
                  2. Monitor container logs<\/strong> after stopping to verify that the service shut down properly.<\/li>\n\n\n\n
                  3. Combine with docker ps<\/code> and filters<\/strong> to target specific containers for stopping.<\/li>\n\n\n\n
                  4. Avoid using -t 0<\/code> unless necessary<\/strong>\u2014give services at least a few seconds to clean up.<\/li>\n\n\n\n
                  5. Automate container shutdowns<\/strong> for scheduled maintenance or batch processing.<\/li>\n<\/ol>\n\n\n\n
                    \n\n\n\n
                    Common Errors and Solutions<\/strong><\/h2>\n\n\n\n
                      \n
                    1. “No such container”<\/strong>
                      \u2192 Ensure the container exists and is running. Check with docker ps<\/code>.<\/li>\n\n\n\n
                    2. “Container failed to stop within the timeout”<\/strong>
                      \u2192 Increase the timeout (-t<\/code>) or use docker kill<\/code> to forcefully stop the container.<\/li>\n\n\n\n
                    3. “Permission denied”<\/strong>
                      \u2192 Ensure you have the necessary permissions or run with sudo<\/code>.<\/li>\n\n\n\n
                    4. Service Does Not Restart Properly<\/strong>
                      \u2192 Check container logs and configuration before restarting.<\/li>\n<\/ol>\n\n\n\n
                      \n\n\n\n
                      Combining docker stop<\/code> with Other Commands<\/strong><\/h2>\n\n\n\n
                      Stop and Remove a Container<\/strong><\/h3>\n\n\n
                      docker stop my_container && docker rm my_container\n<\/code><\/span><\/pre>\n\n\n
                      Stop, Inspect, and Restart<\/strong><\/h3>\n\n\n
                      docker stop my_app\ndocker inspect my_app\ndocker start my_app\n<\/code><\/span><\/pre>\n\n\n
                      \n\n\n\n
                      <\/p>\n","protected":false},"excerpt":{"rendered":"
                      Here\u2019s a complete tutorial on docker stop, including its purpose, how to use it, examples, and use cases. What is docker stop? docker stop is a Docker command used to… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[4862],"tags":[],"class_list":["post-48394","post","type-post","status-publish","format-standard","hentry","category-docker"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48394","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=48394"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48394\/revisions"}],"predecessor-version":[{"id":48396,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48394\/revisions\/48396"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=48394"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=48394"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=48394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}