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

Docker agent on windows fails with Cannot run program "id"

      I'm trying to use a docker agent on windows in declarative pipeline. I can see the image is pulled but then fails as below

      [ply-widgets-project-pipelin-GORWBIPVPM5EWBJECA7BVJBSR5OVNCYISONJIELJYMXAG4YTMWPQ] Running shell script
      sh: sleep: command not found
      sh: sleep: command not found
      sh: sleep: command not found
      sh: sleep: command not found
      sh: sleep: command not found
      + docker inspect -f . 1234567.dkr.ecr.us-west-2.amazonaws.com/builds/jenkins-agent-node:windows-npm-5.8.0
      .
      Cannot run program "id": CreateProcess error=2, The system cannot find the file specified
      

       

      I'm using the following in my jenkinsfile for a stage

      agent {
          docker { 
              image '1234567.dkr.ecr.us-west-2.amazonaws.com/builds/jenkins-agent-node:windows-npm-5.8.0' 
              label 'windows&&docker' 
          }
      }
      

      While I don't think it matters in this case my registry is actually AWS ECR and the agent is a windows server 2016, in a previous stage the following is run to login to ECR

      powershell 'Get-ECRLoginCommand -region us-west-2 | select -ExpandProperty command | Invoke-Expression'
      

          [JENKINS-50857] Docker agent on windows fails with Cannot run program "id"

          abayer not sure if you are the right person to get this looked at by someone but would really appreciate if someone can look at this as docker agent for declarative pipeline is broken for windows containers.

          Jonathan Kuleff added a comment - abayer not sure if you are the right person to get this looked at by someone but would really appreciate if someone can look at this as docker agent for declarative pipeline is broken for windows containers.

          Andrew Bayer added a comment -

          I think that docker-workflow (which is what's used behind the scenes for a Docker agent in Declarative) doesn't support windows, but I could be wrong. I've moved this to the docker-workflow component.

          Andrew Bayer added a comment - I think that docker-workflow (which is what's used behind the scenes for a Docker agent in Declarative) doesn't support windows, but I could be wrong. I've moved this to the docker-workflow component.

          thank you abayer

          Jonathan Kuleff added a comment - thank you abayer

            Unassigned Unassigned
            jonathank Jonathan Kuleff
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: