[JENKINS-33962] docker.inside broken on OSX

Type: Bug
Resolution: Won't Do
Priority: Major
Component/s: docker-workflow-plugin
Labels:
- 2.0-beta
Environment:
OSX 10.11, Docker 1.9.1 / Docker 1.10.3, Pipeline 1.15, Docker Pipeline 1.4, Jenkins 2.0-beta-1

Similar Issues:
Powered by SuggestiMate

Show

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

is related to

JENKINS-33632 docker.inside broken with old client versions

Resolved

JENKINS-34194 docker volume mounts not working as expected when run from within swarm container

Resolved

Keith Zantow created issue - 2016-03-31 19:22

Keith Zantow added a comment - 2016-03-31 19:23

I believe this may be specific to OSX, using boot2docker, which is why I created a new issue rather than reopening: https://issues.jenkins-ci.org/browse/JENKINS-33632

Keith Zantow added a comment - 2016-03-31 19:23 I believe this may be specific to OSX, using boot2docker, which is why I created a new issue rather than reopening: https://issues.jenkins-ci.org/browse/JENKINS-33632

Keith Zantow made changes - 2016-03-31 19:23

Link

New: This issue is related to ~~JENKINS-33632~~ [ ~~JENKINS-33632~~ ]

Keith Zantow made changes - 2016-03-31 19:24

Description

Original: 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:

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

(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:
{code}
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
{code}

New: 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:

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

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

Results in:
{code}
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
{code}

Keith Zantow made changes - 2016-03-31 19:25

Description

Original: 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:

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

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

Results in:
{code}
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
{code}

New: 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:

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

(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:
{code}
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
{code}

Jacob Blain Christen added a comment - 2016-04-12 20:14 - edited

As noted on JENKINS-33632, I am seeing this on 1.642.2 with pipeline/workflow updates prior to the 2.0 split and docker-workflow 1.4. Invoking the command manually that jenkins is invoking and delving into the container, I see that the mounted volumes are showing up as owned by root. I wonder if the 1.9 client going against the 1.10 server is causing this.

Jacob Blain Christen added a comment - 2016-04-12 20:14 - edited As noted on JENKINS-33632 , I am seeing this on 1.642.2 with pipeline/workflow updates prior to the 2.0 split and docker-workflow 1.4. Invoking the command manually that jenkins is invoking and delving into the container, I see that the mounted volumes are showing up as owned by root. I wonder if the 1.9 client going against the 1.10 server is causing this.

Jacob Blain Christen made changes - 2016-04-13 07:15

Link

New: This issue is related to ~~JENKINS-34194~~ [ ~~JENKINS-34194~~ ]

Jesse Glick added a comment - 2016-06-22 15:07

Try the recently released (beta) versions of the native Docker executable for Windows or OS X. Do not plan on supporting boot2docker oddities.

Jesse Glick added a comment - 2016-06-22 15:07 Try the recently released (beta) versions of the native Docker executable for Windows or OS X. Do not plan on supporting boot2docker oddities.

Jesse Glick made changes - 2016-06-22 15:07

Resolution		New: Won't Do [ 10001 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Michael Neale added a comment - 2016-07-14 22:52

yes that type of thing does work on OS-X generally with the beta (I haven't tried wiht the beta from a few days ago).

I have seen other permission errors with more sophisticated pipelines but the basics certainly work well with non boot2docker on OS-X. I can't speak for windows however.

Michael Neale added a comment - 2016-07-14 22:52 yes that type of thing does work on OS-X generally with the beta (I haven't tried wiht the beta from a few days ago). I have seen other permission errors with more sophisticated pipelines but the basics certainly work well with non boot2docker on OS-X. I can't speak for windows however.

Assignee:: Jesse Glick

Reporter:: Keith Zantow

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2016-03-31 19:22

Updated:: 2016-10-05 18:32

Resolved:: 2016-06-22 15:07

Jenkins

Details

Description

Attachments

Issue Links

Activity

Collapse comment: Keith Zantow added a comment - 2016-03-31 19:23

Expand comment: Keith Zantow added a comment - 2016-03-31 19:23

Collapse comment: Jacob Blain Christen added a comment - 2016-04-12 20:14, Edited by Jacob Blain Christen - 2016-04-12 20:14

Expand comment: Jacob Blain Christen added a comment - 2016-04-12 20:14, Edited by Jacob Blain Christen - 2016-04-12 20:14

Collapse comment: Jesse Glick added a comment - 2016-06-22 15:07

Expand comment: Jesse Glick added a comment - 2016-06-22 15:07

Collapse comment: Michael Neale added a comment - 2016-07-14 22:52

Expand comment: Michael Neale added a comment - 2016-07-14 22:52

People

Dates