We are conducting some relatively simple tests with the docker pipeline plugin.  In our test script, we are simply pulling our windows image, and then calling "image.inside()" to run a bat script "echo hello".

       

      However, this causes our pipeline to hang indefinitely.  After some debugging, the only way to get this pipeline to finish successfully is by manually going into the running docker container with our windows image, and running the jenkins-wrap.bat file manually.  This causes the bat step in Jenkins to resolve.  I think there could be a bug in this plugin when calling this jenkins-wrap.bat file for windows.  Our tests on Linux containers works as expected

          [JENKINS-74780] Image inside does not call jenkins-wrap.bat

          Brandon added a comment -

          To sum it up better, our pipeline looks something like:

          withDockerRegistry(...) {
                  image = docker.image(image_name)
                  image.pull()
              } 
          
          image.inside("--entrypoint=''") {
                  bat "echo hello"
          }

          This will start a docker container on our Windows VM, but the pipeline will hang on the `bat` step.  Then, if I log into our VM run a command like:

          docker exec container_id cmd.exe /c path\to\tmp\durable-1234567\jenkins-wrap.bat
          

          The pipeline will finally proceed.  But it will hang indefinitely until I manually trigger this batch file in the durable directory within our container

          Brandon added a comment - To sum it up better, our pipeline looks something like: withDockerRegistry(...) {         image = docker.image(image_name)         image.pull()     } image.inside( "--entrypoint=''" ) { bat "echo hello" } This will start a docker container on our Windows VM, but the pipeline will hang on the `bat` step.  Then, if I log into our VM run a command like: docker exec container_id cmd.exe /c path\to\tmp\durable-1234567\jenkins-wrap.bat The pipeline will finally proceed.  But it will hang indefinitely until I manually trigger this batch file in the durable directory within our container

            Unassigned Unassigned
            czap_2024 Brandon
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: