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

Here\u2019s a complete tutorial<\/strong> on docker kill<\/code>, including its purpose<\/strong>, how it works, and a comprehensive list of examples<\/strong>.<\/p>\n\n\n\n

\n\n\n\n

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

docker kill<\/code> is a Docker command used to immediately stop a running container<\/strong> by sending a specified signal (default is SIGKILL<\/code>). It\u2019s different from docker stop<\/code>, which shuts down the container gracefully by sending SIGTERM<\/code> first and giving the process time to terminate.<\/p>\n\n\n\n

Key Features:<\/strong><\/h3>\n\n\n\n
    \n
  • Forcefully stops<\/strong> a running container.<\/li>\n\n\n\n
  • Sends a custom signal<\/strong> to the main process (e.g., SIGTERM<\/code>, SIGUSR1<\/code>).<\/li>\n\n\n\n
  • Useful for emergency stops<\/strong> or when a container fails to respond to docker stop<\/code>.<\/li>\n\n\n\n
  • Faster than docker stop<\/code><\/strong> because it doesn\u2019t wait for the process to exit.<\/li>\n<\/ul>\n\n\n\n
    \n\n\n\n

    Basic Syntax<\/strong><\/h2>\n\n\n
    docker<\/span> kill<\/span> [OPTIONS]<\/span> CONTAINER<\/span> [CONTAINER...]<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    Options:<\/strong><\/h3>\n\n\n\n
      \n
    • --signal<\/code> \u2192 Specify the signal to send to the container (SIGKILL<\/code>, SIGTERM<\/code>, SIGHUP<\/code>, etc.).<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n
      Difference Between docker kill<\/code> and docker stop<\/code><\/strong><\/h2>\n\n\n\n
      docker kill<\/code><\/strong><\/th>docker stop<\/code><\/strong><\/th><\/tr><\/thead>
      Sends SIGKILL<\/code> by default<\/td>Sends SIGTERM<\/code>, then SIGKILL<\/code> after a timeout<\/td><\/tr>
      Immediate and forceful stop<\/td>Graceful shutdown with time for cleanup<\/td><\/tr>
      Faster<\/td>Slower but safer for running processes<\/td><\/tr>
      Suitable for non-responsive containers<\/td>Suitable for normal shutdowns<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n
      Examples of docker kill<\/code><\/strong><\/h2>\n\n\n\n
      1. Kill a Running Container<\/strong><\/h3>\n\n\n
      docker kill my_container\n<\/code><\/span><\/pre>\n\n\n
      This immediately stops my_container<\/code> by sending the SIGKILL<\/code> signal.<\/p>\n\n\n\n
      \n\n\n\n
      2. Kill Multiple Containers<\/strong><\/h3>\n\n\n
      docker kill container1 container2 container3\n<\/code><\/span><\/pre>\n\n\n
      This kills multiple containers at once.<\/p>\n\n\n\n
      \n\n\n\n
      3. Use a Custom Signal (SIGTERM<\/code>)<\/strong><\/h3>\n\n\n
      docker kill --signal=\"SIGTERM\"<\/span> my_container\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This sends SIGTERM<\/code> to my_container<\/code>, allowing it to shut down more gracefully.<\/p>\n\n\n\n
      \n\n\n\n
      4. Use SIGUSR1<\/code> to Trigger Custom Behavior<\/strong><\/h3>\n\n\n\n
      If your containerized application handles custom signals, you can send SIGUSR1<\/code>:<\/p>\n\n\n
      docker kill --signal=\"SIGUSR1\"<\/span> my_container\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n\n\n\n
      5. Kill All Running Containers<\/strong><\/h3>\n\n\n
      docker kill $(docker ps -q)\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This command kills all currently running containers.<\/p>\n\n\n\n
      \n\n\n\n
      6. Check the Exit Status of a Killed Container<\/strong><\/h3>\n\n\n
      docker inspect --format='{{.State.ExitCode}}'<\/span> my_container\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Returns the exit code (137<\/code> for SIGKILL<\/code>).<\/p>\n\n\n\n
      \n\n\n\n
      7. Use docker kill<\/code> in a Shell Script<\/strong><\/h3>\n\n\n
      #!\/bin\/bash<\/span>\nfor<\/span> container in<\/span> $(docker ps -q); do<\/span>\n  docker kill $container\ndone\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This script kills all running containers one by one.<\/p>\n\n\n\n
      \n\n\n\n
      8. Kill a Container Running an Interactive Process<\/strong><\/h3>\n\n\n\n
      If you have a container running a process that\u2019s stuck, like an interactive bash shell:<\/p>\n\n\n
      docker kill my_interactive_container\n<\/code><\/span><\/pre>\n\n\n
      \n\n\n\n
      9. Send SIGHUP<\/code> to Reload Configuration<\/strong><\/h3>\n\n\n\n
      If your application supports reloading its configuration with SIGHUP<\/code>, you can trigger it:<\/p>\n\n\n
      docker kill --signal=\"SIGHUP\"<\/span> my_app_container\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n\n\n\n
      10. Monitor and Kill Non-Responsive Containers<\/strong><\/h3>\n\n\n
      if<\/span> [ \"$(docker inspect --format='{{.State.Status}}' my_container)\"<\/span> == \"running\"<\/span> ]<\/span>; then<\/span>\n  docker<\/span> kill<\/span> my_container<\/span>\nfi<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      This checks if the container is still running before killing it.<\/p>\n\n\n\n
      \n\n\n\n
      List of Common docker kill<\/code> Commands<\/strong><\/h2>\n\n\n\n
      Command<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
      docker kill my_container<\/code><\/td>Kill a running container with SIGKILL<\/code><\/td><\/tr>
      docker kill --signal=\"SIGTERM\" my_container<\/code><\/td>Send SIGTERM<\/code> to a running container<\/td><\/tr>
      docker kill container1 container2<\/code><\/td>Kill multiple containers<\/td><\/tr>
      docker kill --signal=\"SIGHUP\" my_app_container<\/code><\/td>Send SIGHUP<\/code> to reload configuration<\/td><\/tr>
      docker kill $(docker ps -q)<\/code><\/td>Kill all running containers<\/td><\/tr>
      docker inspect --format='{{.State.ExitCode}}' my_container<\/code><\/td>Check the exit status of a killed container<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n
      Best Practices for Using docker kill<\/code>:<\/strong><\/h2>\n\n\n\n
        \n
      1. Use docker stop<\/code> for graceful shutdowns<\/strong> unless immediate termination is required.<\/li>\n\n\n\n
      2. Send custom signals<\/strong> for applications that support them (e.g., SIGHUP<\/code> for reloads).<\/li>\n\n\n\n
      3. Avoid data loss<\/strong> by ensuring the container\u2019s process does not have unsaved data when killing it.<\/li>\n\n\n\n
      4. Monitor exit codes<\/strong> to understand why a container was killed (137<\/code> indicates SIGKILL<\/code>).<\/li>\n<\/ol>\n\n\n\n
        \n\n\n\n
        Common Errors and Solutions<\/strong><\/h2>\n\n\n\n
          \n
        1. “Cannot kill container: No such container”<\/strong>
          \u2192 Ensure the container is running. Use docker ps<\/code> to check.<\/li>\n\n\n\n
        2. “Permission denied”<\/strong>
          \u2192 You may need elevated permissions (sudo<\/code>) to kill certain containers.<\/li>\n\n\n\n
        3. Container keeps restarting<\/strong>
          \u2192 If the container is configured with a restart policy (--restart always<\/code>), it will restart after being killed. Stop it with: docker stop my_container docker rm my_container<\/code><\/li>\n<\/ol>\n\n\n\n
          \n\n\n\n
          Exit Codes Explained<\/strong><\/h2>\n\n\n\n
            \n
          • 137<\/code> \u2192 The container was killed with SIGKILL<\/code>.<\/li>\n\n\n\n
          • 143<\/code> \u2192 The container was stopped with SIGTERM<\/code>.<\/li>\n<\/ul>\n\n\n\n
            \n\n\n\n
            <\/p>\n","protected":false},"excerpt":{"rendered":"
            Here\u2019s a complete tutorial on docker kill, including its purpose, how it works, and a comprehensive list of examples. What is docker kill? docker kill is a Docker command used… <\/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-48366","post","type-post","status-publish","format-standard","hentry","category-docker"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48366","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=48366"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48366\/revisions"}],"predecessor-version":[{"id":48368,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48366\/revisions\/48368"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=48366"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=48366"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=48366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}