Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-59893

bat calls hang in Windows Docker container in declarative pipeline script

    XMLWordPrintable

Details

    Description

      Description

      bat steps hang (endless spinning wheel in the jobs console output) even for simple Windows containers.

      bat "echo test inside"

      Troubleshooting & Additional info

      powershell and all other commands tried so far work without issue. Even using powershell to wrap cmd.exe commands works fine. Example:

       

      powershell "cmd /c echo test inside"

       

      Running the image manually on the node host exhibits no issues. i.e. can run docker run -it microsoft/windowsservercore:ltsc2016 and happy use cmd and all other commands without issue.

      Similarly we can attach to the container spun up by the Jenkins job while it's hung and execute the same echo command (or any other) without issue.

      Others have not had this issue so it could be something specific in our setup, but I have not been able to pinpoint anything. https://github.com/jenkinsci/docker-workflow-plugin/pull/184#issuecomment-539213785

      The job console output shows no errors and neither does the main Jenkins log under /log/all. No errors if any kind while the job is running / hung.

      Setup

      Jenkins node host: Windows Server 2016 (1607)

      Docker image: microsoft/windowsservercore:ltsc2016

      Happens regardless if docker {} or dockerfile {} syntax is used.

      Specifically using declarative pipeline scripts. Have not tested other methods

      pipeline {
          agent {
              docker {
                  image 'microsoft/windowsservercore:ltsc2016'
                  label 'windows'
              }
          }
          stages {
              stage('Example Build') {
                  steps{
                      bat "echo test inside"
                  }
              }
          }
      }

      Attachments

        Activity

          solvingj jerry wiltse added a comment -

          This matrix is how I learned about it.  It might be helpful to you: https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility

          solvingj jerry wiltse added a comment - This matrix is how I learned about it.  It might be helpful to you:  https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility
          stuck_tech a b added a comment -

          We've now tried this on a Windows Server 2019 host (1809) and a vanilla{{ }}mcr.microsoft.com/windows/servercore:1809 image and the bat call still hangs.  Even worse when we try a nanoserver image such as mcr.microsoft.com/powershell:nanoserver-1809 it will hang on both powershell and bat and when the Jenkins job is manually cancelled the server will experience a critical error and reboot itself!

           

          Critical: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

           

          stuck_tech a b added a comment - We've now tried this on a Windows Server 2019 host (1809) and a vanilla{{ }} mcr.microsoft.com/windows/servercore:1809 image and the bat call still hangs.  Even worse when we try a nanoserver image such as  mcr.microsoft.com/powershell:nanoserver-1809 it will hang on both powershell and bat and when the Jenkins job is manually cancelled the server will experience a critical error and reboot itself!   Critical: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.  

          How did you install docker?
          Please follow this guide
          https://docs.docker.com/install/windows/docker-ee/

          casz Joseph Petersen (old) added a comment - How did you install docker? Please follow this guide https://docs.docker.com/install/windows/docker-ee/
          stuck_tech a b added a comment -

          That is the method we used for install.

          The curious thing is that sometimes the bat calls work. We have some large and complex pipeline scripts in which many or even most of the bat calls will work but some still fail and the hello world example above fails ever time.

          I suspect that something else in the larger pipelines are inadvertently sidestepping / “fixing” the issue in real time. So there might be some kind of context in which the calls work and another (like the hello world) where they don’t. Haven’t been able to narrow it down yet.

          stuck_tech a b added a comment - That is the method we used for install. The curious thing is that sometimes the bat calls work. We have some large and complex pipeline scripts in which many or even most of the bat calls will work but some still fail and the hello world example above fails ever time. I suspect that something else in the larger pipelines are inadvertently sidestepping / “fixing” the issue in real time. So there might be some kind of context in which the calls work and another (like the hello world) where they don’t. Haven’t been able to narrow it down yet.

          Wish I could help you but we haven't experienced the issue

          casz Joseph Petersen (old) added a comment - Wish I could help you but we haven't experienced the issue

          People

            Unassigned Unassigned
            stuck_tech a b
            Votes:
            4 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated: