[JIRA] [docker-workflow-plugin] (JENKINS-33962) docker.inside broken on OSX
Title: Message Title Jacob Blain Christen commented on JENKINS-33962 Re: docker.inside broken on OSX As noted on https://issues.jenkins-ci.org/browse/JENKINS-33632?focusedCommentId=254211=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-254211 , 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-33962) docker.inside broken on OSX
Title: Message Title Jacob Blain Christen edited a comment on JENKINS-33962 Re: docker.inside broken on OSX As noted on [ JENKINS-33632| https://issues.jenkins-ci.org/browse/JENKINS-33632?focusedCommentId=254211=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-254211 |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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-33962) docker.inside broken on OSX
Title: Message Title
Keith Zantow updated an issue
Jenkins / JENKINS-33962
docker.inside broken on OSX
Change By:
Keith Zantow
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 scriptsh: 1: cannot create /jenkins/2.0-beta-1/workspace/pipeline@tmp/durable-a6ff18c8/pid: Directory nonexistentsh: 1: cannot create /jenkins/2.0-beta-1/workspace/pipeline@tmp/durable-a6ff18c8/jenkins-log.txt: Directory nonexistentsh: 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 PipelineERROR: script returned exit code -2Finished: FAILURE{code}
Add Comment
[JIRA] [docker-workflow-plugin] (JENKINS-33962) docker.inside broken on OSX
Title: Message Title
Keith Zantow updated an issue
Jenkins / JENKINS-33962
docker.inside broken on OSX
Change By:
Keith Zantow
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 scriptsh: 1: cannot create /jenkins/2.0-beta-1/workspace/pipeline@tmp/durable-a6ff18c8/pid: Directory nonexistentsh: 1: cannot create /jenkins/2.0-beta-1/workspace/pipeline@tmp/durable-a6ff18c8/jenkins-log.txt: Directory nonexistentsh: 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 PipelineERROR: script returned exit code -2Finished: FAILURE{code}
Add Comment
[JIRA] [docker-workflow-plugin] (JENKINS-33962) docker.inside broken on OSX
Title: Message Title Keith Zantow commented on JENKINS-33962 Re: docker.inside broken on OSX 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 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-33962) docker.inside broken on OSX
Title: Message Title
Keith Zantow created an issue
Jenkins / JENKINS-33962
docker.inside broken on OSX
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
docker-workflow-plugin
Created:
2016/Mar/31 7:22 PM
Environment:
OSX 10.11, Docker 1.9.1 / Docker 1.10.3, Pipeline 1.15, Docker Pipeline 1.4, Jenkins 2.0-beta-1
Labels:
2.0-beta
Priority:
Major
Reporter:
Keith Zantow
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
