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

Docker pipeline: 'absolute path' error when running linux container under windows host

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: docker-workflow-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.164.1
      Docker Pipeline 1.21
      Pipeline 2.6
      Windows 10
    • Similar Issues:

      Description

      I have a jenkins master on linux, a slave agent on windows 10. On the slave there is docker desktop installed. I can run commands under this docker from windows command line, for example:

      docker run --rm -v c:/Users/modtest:/home/pkruk node:alpine sh -c "ls -la"
      total 64
      drwxr-xr-x 1 root root 4096 Dec 12 17:09 .
      drwxr-xr-x 1 root root 4096 Dec 12 17:09 ..
      -rwxr-xr-x 1 root root 0 Dec 12 17:09 .dockerenv
      [...] 

      But when I try to execute following pipeline:

      pipeline {
          agent {
              docker { image 'node:alpine' }
          }
          stages {
              stage('Build') {
                  environment {
                      HOME = '.'
                  }
                  steps {
                      sh 'rm -f *.vsix'
                  }
                  post {
                      always {
                          archiveArtifacts artifacts: '*.vsix', fingerprint: true
                      }
                  }
              }
          }
      } 

      I get following error:

      Started by user pkruk
      Obtained Jenkinsfile from git [...]
      Running in Durability level: PERFORMANCE_OPTIMIZED
      [Pipeline] Start of Pipeline
      [Pipeline] node
      Running on piwon in C:\Jenkins\workspace\priv.pkruk
      [Pipeline] {
      [Pipeline] stage
      [Pipeline] { (Declarative: Checkout SCM)
      [Pipeline] checkout
      [...]
      [Pipeline] }
      [Pipeline] // stage
      [Pipeline] withEnv
      [Pipeline] {
       > git rev-list --no-walk c05145e1abded6851debb54aa8e76bb1151e3fad # timeout=10
      [Pipeline] isUnix
      [Pipeline] batC:\Jenkins\workspace\priv.pkruk>docker inspect -f . node:alpine 
      .
      [Pipeline] withDockerContainer
      piwon does not seem to be running inside a container
      [Pipeline] // withDockerContainer
      [Pipeline] }
      [Pipeline] // withEnv
      [Pipeline] }
      [Pipeline] // node
      [Pipeline] End of Pipeline
      java.io.IOException: Failed to run image 'node:alpine'. Error: docker: Error response from daemon: the working directory 'C:/Jenkins/workspace/priv.pkruk/' is invalid, it needs to be an absolute path.
      See 'docker run --help'.
      	at org.jenkinsci.plugins.docker.workflow.client.WindowsDockerClient.run(WindowsDockerClient.java:57)
      	at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:199)
      	at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286)
      	at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179)
      	at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
      	at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48)
      	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
      	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
      	at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)
      	at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(Docker.groovy:126)
      	at org.jenkinsci.plugins.docker.workflow.Docker.node(Docker.groovy:66)
      	at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(Docker.groovy:114)
      	at org.jenkinsci.plugins.pipeline.modeldefinition.agent.impl.DockerPipelineScript.runImage(DockerPipelineScript.groovy:54)
      	at org.jenkinsci.plugins.pipeline.modeldefinition.agent.impl.AbstractDockerPipelineScript.configureRegistry(AbstractDockerPipelineScript.groovy:73)
      	at org.jenkinsci.plugins.pipeline.modeldefinition.agent.impl.AbstractDockerPipelineScript.run(AbstractDockerPipelineScript.groovy:52)
      	at org.jenkinsci.plugins.pipeline.modeldefinition.agent.CheckoutScript.checkoutAndRun(CheckoutScript.groovy:61)
      	at ___cps.transform___(Native Method)
      	at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)
      	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)
      	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)
      	at sun.reflect.GeneratedMethodAccessor325.invoke(Unknown Source)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:498)
      	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
      	at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46)
      	at com.cloudbees.groovy.cps.Next.step(Next.java:83)
      	at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
      	at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
      	at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
      	at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
      	at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
      	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
      	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
      	at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:185)
      	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:405)
      	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:96)
      	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:317)
      	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:281)
      	at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
      	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
      	at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:748)
      Finished: FAILURE 

      I found a couple of SO posts with the same error but they offer no real solution:

      https://stackoverflow.com/questions/58447566/jenkins-pipeline-docker-agent-docker-run-error-failed-to-run-image-java-io

      https://stackoverflow.com/questions/56136415/jenkins-windows-docker-fails-to-run-image-working-directory-is-invalid-it-need

       

        Attachments

          Activity

          Hide
          jamespan James Pan added a comment -

          Hi All,

          I am facing the same issue now and wondering if the problem has been solved? When I use Docker Desktop on windows, I usually use the following argument to map a path on my window host to a linux docker

          -v /d/jenkins_data:/var/jenkins_home

          I am wondering if this is the issue course the error because I have searched on the internet and lots of post described docker doesn't support path format in windows format.

          Show
          jamespan James Pan added a comment - Hi All, I am facing the same issue now and wondering if the problem has been solved? When I use Docker Desktop on windows, I usually use the following argument to map a path on my window host to a linux docker -v /d/jenkins_data:/ var /jenkins_home I am wondering if this is the issue course the error because I have searched on the internet and lots of post described docker doesn't support path format in windows format.
          Hide
          jamespan James Pan added a comment -

          I thing I have found the root course. When I use a docker image with the same type of the host, it's fine, however, when I use a docker image which is different from the host, this plugin will have exceptions. For example, if the host is a windows and wanted to use a linux image as the slave, then working directory will not work because D:\ or C:\ is not a absolution path in the linux system, that must be changed to /d or /c.

          However, since the host is a windows, the WindowsDockerClient will be used and cmd.exe will be run in the linux image, and that will lead to another exception. The conclusion is to use an image which align with the host.

          I haven't tested on a Mac but I think Mac<>Linux will be fine but Mac<>Windows will still have the same issue.

          Show
          jamespan James Pan added a comment - I thing I have found the root course. When I use a docker image with the same type of the host, it's fine, however, when I use a docker image which is different from the host, this plugin will have exceptions. For example, if the host is a windows and wanted to use a linux image as the slave, then working directory will not work because D:\ or C:\ is not a absolution path in the linux system, that must be changed to /d or /c. However, since the host is a windows, the WindowsDockerClient will be used and cmd.exe will be run in the linux image, and that will lead to another exception. The conclusion is to use an image which align with the host. I haven't tested on a Mac but I think Mac< >Linux will be fine but Mac< >Windows will still have the same issue.
          Hide
          atoro Alex added a comment -

          Thanks for all the hard work here but I am still at a loss to understand how to resolve the issue with Jenkins or Docker not figuring out which path to use.  I have the exact error as started in this post.  I am running Jenkins on WIndows and the goal is to run a linux container on a windows host (running a linux vm).   What I noticed when modifying the config.xml to a path like /c/users/mydir/ the output produced is $ docker run -d -t -w C:/c/users/mydir.  All I was trying to do is figure out what configuration I can change to convert it to a path that linux likes and I cannot figure out how to tell Jenkins to create the right path.  I know what I did is not the solution (again trying to repro the problem).

          Is there a single configuration item somewhere that tells jenkins to do this

          $ docker run -d -t -w /c/users/

          instead of this?

          $ docker run -d -t -w C:/users/

           

          Show
          atoro Alex added a comment - Thanks for all the hard work here but I am still at a loss to understand how to resolve the issue with Jenkins or Docker not figuring out which path to use.  I have the exact error as started in this post.  I am running Jenkins on WIndows and the goal is to run a linux container on a windows host (running a linux vm).   What I noticed when modifying the config.xml to a path like /c/users/mydir/ the output produced is $ docker run -d -t -w C: /c/users/mydir.  All I was trying to do is figure out what configuration I can change to convert it to a path that linux likes and I cannot figure out how to tell Jenkins to create the right path.  I know what I did is not the solution (again trying to repro the problem). Is there a single configuration item somewhere that tells jenkins to do this $ docker run -d -t -w /c/users/ instead of this? $ docker run -d -t -w C:/users/  
          Hide
          shimpossible shim added a comment -

          The updates Eric Schneider made in https://github.com/mrsonicblue/docker-workflow-plugin fixes the issue.  If using an older version of Docker you'll get a "The container started but didn't run the expected command" or "process apparently never started" due to how BusyBox returns output from the "top" command.  BusyBox 'ps' command prints the cat command as "{cat}", so it looks like it never spawned.    I created a PR (https://github.com/mrsonicblue/docker-workflow-plugin/pull/1) that changes the code to also look for {cat} and [cat].   This should make it work in the general case

           

           

          Show
          shimpossible shim added a comment - The updates Eric Schneider made in  https://github.com/mrsonicblue/docker-workflow-plugin  fixes the issue.  If using an older version of Docker you'll get a "The container started but didn't run the expected command" or "process apparently never started" due to how BusyBox returns output from the "top" command.  BusyBox 'ps' command prints the cat command as "{cat}", so it looks like it never spawned.    I created a PR ( https://github.com/mrsonicblue/docker-workflow-plugin/pull/1)  that changes the code to also look for {cat} and [cat] .   This should make it work in the general case    
          Hide
          materigoprecitec Mate Rigo added a comment -

          Thanks shim for your response.

          The only thing I do not understand: why weren't any of the pull requests approved?

          https://github.com/jenkinsci/docker-workflow-plugin/pull/197

          https://github.com/jenkinsci/docker-workflow-plugin/pull/234

          https://github.com/jenkinsci/docker-workflow-plugin/pull/235

          I mean this is a serious issue, for which there seems to be a solution.

           

          This was my intention to have a single slave machine which is running win10 and every build job would be performed in a docker container regardless if it was a windows native or linux native build.

          In the end this is the ultimate promise of containerization to once create the containers and execute them regardless of the host.

          Cheers!

          Show
          materigoprecitec Mate Rigo added a comment - Thanks shim for your response. The only thing I do not understand: why weren't any of the pull requests approved? https://github.com/jenkinsci/docker-workflow-plugin/pull/197 https://github.com/jenkinsci/docker-workflow-plugin/pull/234 https://github.com/jenkinsci/docker-workflow-plugin/pull/235 I mean this is a serious issue, for which there seems to be a solution.   This was my intention to have a single slave machine which is running win10 and every build job would be performed in a docker container regardless if it was a windows native or linux native build. In the end this is the ultimate promise of containerization to once create the containers and execute them regardless of the host. Cheers!

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            pkruk Piotr Krukowiecki
            Votes:
            11 Vote for this issue
            Watchers:
            15 Start watching this issue

              Dates

              Created:
              Updated: