docker.inside broken on OSX

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      This Pipeline script fails, with the same error reported in https://issues.jenkins-ci.org/browse/JENKINS-33632

      Installed fresh from latest .war file, installed default plugins, added Docker Pipeline, created a job `pipeline`, with the given script:

      node {
          docker.image('maven:3.3.3-jdk-8').inside{
              sh "echo success!"
          }
      }
      

      (Note: I also tried this with/without a node wrapper, with/without the UID hack .inside('-u 1000:50'), but all resulted in the same issue.

      Results in:

      Running on master in /jenkins/2.0-beta-1/workspace/pipeline
      [Pipeline] node {
      [Pipeline] sh
      [pipeline] Running shell script
      + docker inspect -f . maven:3.3.3-jdk-8
      .
      [Pipeline] Run build steps inside a Docker container : Start
      $ docker run -t -d -u 501:20 -w /jenkins/2.0-beta-1/workspace/pipeline -v /jenkins/2.0-beta-1/workspace/pipeline:/jenkins/2.0-beta-1/workspace/pipeline:rw -v /jenkins/2.0-beta-1/workspace/pipeline@tmp:/jenkins/2.0-beta-1/workspace/pipeline@tmp:rw -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** maven:3.3.3-jdk-8 cat
      [Pipeline] withDockerContainer {
      [Pipeline] sh
      [pipeline] Running shell script
      sh: 1: cannot create /jenkins/2.0-beta-1/workspace/pipeline@tmp/durable-a6ff18c8/pid: Directory nonexistent
      sh: 1: cannot create /jenkins/2.0-beta-1/workspace/pipeline@tmp/durable-a6ff18c8/jenkins-log.txt: Directory nonexistent
      sh: 1: cannot create /jenkins/2.0-beta-1/workspace/pipeline@tmp/durable-a6ff18c8/jenkins-result.txt: Directory nonexistent
      [Pipeline] } //withDockerContainer
      $ docker stop d47b360cdc3f9e180355415a44ae5a62afc1c2e1ab69c96e4f4d03f9f7daac71
      $ docker rm -f d47b360cdc3f9e180355415a44ae5a62afc1c2e1ab69c96e4f4d03f9f7daac71
      [Pipeline] Run build steps inside a Docker container : End
      [Pipeline] } //node
      [Pipeline] Allocate node : End
      [Pipeline] End of Pipeline
      ERROR: script returned exit code -2
      Finished: FAILURE
      

            Assignee:
            Jesse Glick
            Reporter:
            Keith Zantow
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: