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

Here\u2019s a complete tutorial<\/strong> on docker wait<\/code>, covering what it does<\/strong>, examples<\/strong>, and use cases<\/strong>.<\/p>\n\n\n\n

\n\n\n\n

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

docker wait<\/code> is a Docker command that blocks until a container stops<\/strong> and then returns the container\u2019s exit code<\/strong>. It\u2019s useful for synchronizing tasks<\/strong>, monitoring container completion<\/strong>, and handling exit status<\/strong> in scripts or automation processes.<\/p>\n\n\n\n

Key Features:<\/strong><\/h3>\n\n\n\n
    \n
  • Waits for one or more containers to stop<\/strong>.<\/li>\n\n\n\n
  • Returns the exit status code<\/strong> of the container\u2019s main process.<\/li>\n\n\n\n
  • Ideal for scripting and automation<\/strong>, especially when you need to act based on the container\u2019s success or failure.<\/li>\n<\/ul>\n\n\n\n
    \n\n\n\n

    Basic Syntax<\/strong><\/h2>\n\n\n
    docker<\/span> wait<\/span> CONTAINER<\/span> [CONTAINER...]<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    Arguments:<\/strong><\/h3>\n\n\n\n
      \n
    • CONTAINER<\/code>: The name or ID of the container. You can specify multiple containers.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n
      Examples of docker wait<\/code><\/strong><\/h2>\n\n\n\n
      1. Wait for a Single Container to Stop<\/strong><\/h3>\n\n\n
      docker wait my_container\n<\/code><\/span><\/pre>\n\n\n
      This blocks until my_container<\/code> stops and then returns its exit code.<\/p>\n\n\n\n
      \n\n\n\n
      2. Wait for a Container by ID<\/strong><\/h3>\n\n\n
      docker wait a1b2c3d4e5f6\n<\/code><\/span><\/pre>\n\n\n
      This waits for the container with ID a1b2c3d4e5f6<\/code> to stop.<\/p>\n\n\n\n
      \n\n\n\n
      3. Wait for Multiple Containers<\/strong><\/h3>\n\n\n
      docker wait container1 container2 container3\n<\/code><\/span><\/pre>\n\n\n
      This waits for all specified containers to stop and returns their exit codes in the order they are specified.<\/p>\n\n\n\n
      Example Output:<\/strong><\/p>\n\n\n
      0\n1\n137\n<\/code><\/span><\/pre>\n\n\n
      \n\n\n\n
      4. Wait for a Container in a Script<\/strong><\/h3>\n\n\n
      #!\/bin\/bash<\/span>\ndocker run --name my_temp_container ubuntu sleep 10<\/span> &\ndocker wait my_temp_container\necho<\/span> \"my_temp_container has stopped.\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This script waits for my_temp_container<\/code> to stop and then prints a message.<\/p>\n\n\n\n
      \n\n\n\n
      5. Check the Exit Code of a Container<\/strong><\/h3>\n\n\n
      exit_code=$(docker wait my_container)\necho \"Container exited with code: $exit_code\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This captures the container\u2019s exit code in a variable for further use.<\/p>\n\n\n\n
      \n\n\n\n
      6. Wait for the Last Created Container<\/strong><\/h3>\n\n\n
      docker wait $(docker ps -lq)\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This waits for the last created container to stop.<\/p>\n\n\n\n
      \n\n\n\n
      7. Use in a CI\/CD Pipeline<\/strong><\/h3>\n\n\n
      docker run --name test_container my_app:latest\ndocker wait test_container\nif<\/span> [ $? -eq 0<\/span> ]; then\n  echo<\/span> \"Container completed successfully.\"<\/span>\nelse<\/span>\n  echo<\/span> \"Container failed.\"<\/span>\nfi\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      In this example, docker wait<\/code> checks the exit code and performs an action based on success or failure.<\/p>\n\n\n\n
      \n\n\n\n
      8. Handle Parallel Containers<\/strong><\/h3>\n\n\n
      docker run --name job1 ubuntu sleep 5<\/span> &\ndocker run --name job2 ubuntu sleep 10<\/span> &\ndocker wait job1 job2\necho<\/span> \"Both containers have stopped.\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This waits for both containers (job1<\/code> and job2<\/code>) to stop.<\/p>\n\n\n\n
      \n\n\n\n
      Use Cases for docker wait<\/code><\/strong><\/h2>\n\n\n\n
      1. Synchronization in Automation Scripts<\/strong><\/h3>\n\n\n\n
        \n
      • Wait for containers to finish before moving to the next task.<\/li>\n\n\n\n
      • Example: Run tests<\/strong> in a container and only proceed if they pass.<\/li>\n<\/ul>\n\n\n\n
        2. Monitoring Container Completion<\/strong><\/h3>\n\n\n\n
          \n
        • Monitor batch jobs or background tasks and act based on their exit status.<\/li>\n\n\n\n
        • Example: Process large data files in a container and only continue if the job completes successfully.<\/li>\n<\/ul>\n\n\n\n
          3. CI\/CD Pipelines<\/strong><\/h3>\n\n\n\n
            \n
          • Use docker wait<\/code> to ensure that tests or builds inside containers have finished before deploying.<\/li>\n\n\n\n
          • Example: In a CI pipeline, wait for a containerized test runner to finish and act on its result.<\/li>\n<\/ul>\n\n\n\n
            4. Error Handling and Recovery<\/strong><\/h3>\n\n\n\n
              \n
            • Check the exit status code<\/strong> of a container to detect failures and trigger recovery actions.<\/li>\n\n\n\n
            • Example: Restart a service if a container exits with a non-zero code.<\/li>\n<\/ul>\n\n\n\n
              5. Running Multiple Dependent Containers<\/strong><\/h3>\n\n\n\n
                \n
              • Wait for a dependent service to stop before starting the next one.<\/li>\n\n\n\n
              • Example: Wait for a database migration container<\/strong> to finish before starting the main app.<\/li>\n<\/ul>\n\n\n\n
                \n\n\n\n
                List of Common docker wait<\/code> Commands<\/strong><\/h2>\n\n\n\n
                Command<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
                docker wait my_container<\/code><\/td>Wait for a single container to stop<\/td><\/tr>
                docker wait container1 container2<\/code><\/td>Wait for multiple containers to stop<\/td><\/tr>
                docker wait a1b2c3d4e5f6<\/code><\/td>Wait for a container by its ID<\/td><\/tr>
                docker wait $(docker ps -lq)<\/code><\/td>Wait for the last created container<\/td><\/tr>
                docker run --name temp ubuntu sleep 5 & docker wait temp<\/code><\/td>Run a container and wait for it to finish<\/td><\/tr>
                exit_code=$(docker wait my_container)<\/code><\/td>Capture the container\u2019s exit code<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                \n\n\n\n
                Best Practices for Using docker wait<\/code>:<\/strong><\/h2>\n\n\n\n
                  \n
                1. Use in automation scripts<\/strong> to manage container completion and handle exit statuses.<\/li>\n\n\n\n
                2. Combine with docker logs<\/code><\/strong> to inspect why a container stopped.<\/li>\n\n\n\n
                3. Monitor exit codes<\/strong> and trigger appropriate actions for success or failure.<\/li>\n\n\n\n
                4. Avoid blocking unnecessarily<\/strong>\u2014use it only when you need to wait for container completion.<\/li>\n\n\n\n
                5. Combine with docker run --rm<\/code><\/strong> for temporary containers that clean up automatically after completion.<\/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 has not been removed. Check with docker ps -a<\/code>.<\/li>\n\n\n\n
                  2. “Container is still running” (No immediate output)<\/strong>
                    \u2192 This is expected behavior; docker wait<\/code> will block until the container stops.<\/li>\n\n\n\n
                  3. Exit Code is Non-Zero<\/strong>
                    \u2192 Check the container logs (docker logs my_container<\/code>) to identify the cause of failure.<\/li>\n<\/ol>\n\n\n\n
                    \n\n\n\n
                    Combining docker wait<\/code> with Other Commands<\/strong><\/h2>\n\n\n\n
                    Run, Wait, and Remove a Container<\/strong><\/h3>\n\n\n
                    docker run --rm --name temp_container ubuntu sleep 10 &\ndocker wait temp_container\n<\/code><\/span><\/pre>\n\n\n
                    Log the Output and Check Exit Code<\/strong><\/h3>\n\n\n
                    docker run --name my_app my_image\ndocker logs my_app\nexit_code=$(docker wait my_app)\necho \"Exit code: $exit_code\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    \n\n\n\n
                    <\/p>\n","protected":false},"excerpt":{"rendered":"
                    Here\u2019s a complete tutorial on docker wait, covering what it does, examples, and use cases. What is docker wait? docker wait is a Docker command that blocks until a container… <\/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-48403","post","type-post","status-publish","format-standard","hentry","category-docker"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48403","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=48403"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48403\/revisions"}],"predecessor-version":[{"id":48405,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48403\/revisions\/48405"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=48403"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=48403"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=48403"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}