-
Bug
-
Resolution: Unresolved
-
Minor
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" } } } }
henryborchers Which version are you currently running? We installed fresh just a couple weeks ago but I can't check the version right now.
casz Our current server is 2016 thus we cannot use base images beyond microsoft/windowsservercore:ltsc2016 more or less. As per henryborchers 2019 host and images can exhibit the same issues.
However, for other reasons we need to provision a second server so we are shooting for 2019. I will try to keep the rest of the setup the same and see if we experience the same issue.
Our use case is different and we are not running Jenkins agents inside the container, but I suppose we could try that Jenkins image you reference if we continue to have problems on 2019. We won't be able to use it on 2016 because it seems to be based on windowsservercore 1809 which is beyond what we can run on 2016 as far as I can tell.
Edit: Confirmed...