[JIRA] (JENKINS-33632) docker.inside broken with old client versions
Title: Message Title Jesse Glick resolved as Won't Fix Warning added with https://github.com/jenkinsci/docker-workflow-plugin/pull/80, thanks! Jenkins / JENKINS-33632 docker.inside broken with old client versions Change By: Jesse Glick Status: Reopened Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-33632) docker.inside broken with old client versions
Title: Message Title Jesse Glick assigned an issue to Pierre Beitz Jenkins / JENKINS-33632 docker.inside broken with old client versions Change By: Jesse Glick Assignee: Jesse Glick Pierre Beitz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken with old client versions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33632 Re: docker.inside broken with old client versions Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java http://jenkins-ci.org/commit/docker-workflow-plugin/98d2af626cca98f05d358c11431c9f0b5600809b Log: Merge pull request #80 from PierreBtz/dev JENKINS-33632 Add a warning if the detected docker version is less than v1.8 Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/eb142f64eba3...98d2af626cca Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken with old client versions
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33632 docker.inside broken with old client versions Change By: Jesse Glick Summary: docker.inside broken with old client versions Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Pierre Beitz commented on JENKINS-33632 Re: docker.inside broken I had a look at the non working and working environment and came up with the following: working Client: Version: 1.12.3 API version: 1.24 Server: Version: 1.12.3 API version: 1.24 non working Client version: 1.6.2 Client API version: 1.18 Server version: 1.12.3 Server API version: 1.24 I guess the client version is the one the plugin should look at then. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Jesse Glick commented on JENKINS-33632 Re: docker.inside broken There is already a minimum client version specified in the plugin, so this could be updated (or is it the server version which matters?), or we could expand the list of parsable formats. Either way, definitely it would be nice for the plugin to print more helpful diagnostics. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Pierre Beitz commented on JENKINS-33632 Re: docker.inside broken Hello again, You are absolutely right and I went debugging again to find out...that the issue was on my side To give more context for people coming here, it is in fact the docker that was inside my jenkins docker image that was not correct. I installed it using apt-get install from the official jenkins image which was a mistake as I ended up with a docker client version 1.6.2 (communicating with a docker deamon on my host running a version 12...). The problem finally came from the fact the docker inspect output format was changed for volumes in docker 1.8 (I'm pretty sure this comes from this PR). As a consequence, the plugin did not find any volumes, falling back to a --volume mount. Installing the latest version of docker using curl -sSL https://get.docker.com/ | sh solved the issue. I guess this means the issue can be closed. If you are interested, I made a pull request to add an error in the logs saying : "The docker version is less than v1.8. Running a 'docker.inside' from inside a container will not work." Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title
Jesse Glick commented on JENKINS-33632
Re: docker.inside broken
I think the test is not correct. When I amended it as follows
diff --git a/src/test/java/org/jenkinsci/plugins/docker/workflow/client/DockerClientTest.java b/src/test/java/org/jenkinsci/plugins/docker/workflow/client/DockerClientTest.java
index 2edee8e..5e665c7 100644
--- a/src/test/java/org/jenkinsci/plugins/docker/workflow/client/DockerClientTest.java
+++ b/src/test/java/org/jenkinsci/plugins/docker/workflow/client/DockerClientTest.java
@@ -94,15 +94,17 @@ public class DockerClientTest {
public void test_cgroup_string_matching() {
final String[] possibleCgroupStrings = new String[] {
- "2:cpu:/docker/3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b",
- "4:cpuset:/system.slice/docker-3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b.scope"
+"2:cpu:/docker/3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b",
+"4:cpuset:/system.slice/docker-3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b.scope",
+"3:cpu:/docker/3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b",
+"2:cpuset:/docker/3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b",
};
for (final String possibleCgroupString : possibleCgroupStrings) {
final Pattern pattern = Pattern.compile(DockerClient.CGROUP_MATCHER_PATTERN);
Matcher matcher = pattern.matcher(possibleCgroupString);
- Assert.assertTrue(matcher.find());
- Assert.assertEquals("3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b", matcher.group(1));
+ Assert.assertTrue(possibleCgroupString, matcher.find());
+ Assert.assertEquals(possibleCgroupString, "3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b", matcher.group(1));
}
}
it passes.
Add Comment
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title
Pierre Beitz commented on JENKINS-33632
Re: docker.inside broken
Thank you for your answer. I had a quick look to the code, and wrote a failing unit test (that you can also find in the gist):
@Test
public void test_cgroup_string_matching_bug() {
final String[] possibleCgroupStrings = new String[] {
"14:name=systemd:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"13:pids:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"12:hugetlb:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"11:net_prio:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"10:perf_event:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"9:net_cls:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"8:freezer:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"7:devices:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"6:memory:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"5:blkio:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"4:cpuacct:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"3:cpu:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"2:cpuset:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"1:name=openrc:/docker"
};
for (final String possibleCgroupString : possibleCgroupStrings) {
final Pattern pattern = Pattern.compile(DockerClient.CGROUP_MATCHER_PATTERN);
Matcher matcher = pattern.matcher(possibleCgroupString);
Assert.assertTrue(matcher.find());
Assert.assertEquals("45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11", matcher.group(1));
}
}
As you can see, the pattern is not matching one of the known cgroup formats. I have no idea how to proceed from there. Note that I extracted this pattern from a docker running on top of windows 10. I also have the problem on Linux Mint, I can extract the content of the /proc/self/cgroup on it too if it can help.
Add Comment
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title Jesse Glick reopened an issue The errors from sh are irrelevant; the point is that your docker run command is missing --volumes-from. Offhand I do not know why. Someday when I have time I will try to follow the steps to reproduce and track down the problem. Jenkins / JENKINS-33632 docker.inside broken Change By: Jesse Glick Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title
Pierre Beitz edited a comment on JENKINS-33632
Re: docker.inside broken
Hello [~jglick],I think I found a self-contained example showing that the issue is still around. Using the following versions of Docker* Docker 1.12.2, build bb80604 (on linux).* Docker 1.12.3, build 6b644ec, experimental (on windows).And using [this gist|https://gist.github.com/PierreBtz/9bf58de96fdf5f0b0f272cba850f1161], I ended up with the following error on my two machines:{noformat}$ docker run -t -d -u 1000:1000 -w /var/jenkins_home/jobs/demo/workspace -v /var/jenkins_home/jobs/demo/workspace:/var/jenkins_home/jobs/demo/workspace:rw -v /var/jenkins_home/jobs/demo/workspace@tmp:/var/jenkins_home/jobs/demo/workspace@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e -e --entrypoint cat ubuntu[Pipeline] {[Pipeline] sh[workspace] Running shell scriptsh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/pid: Directory nonexistentsh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-log.txt: Directory nonexistentsh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-result.txt: Directory nonexistent{noformat}Version of the Docker pipeline is 1.9.1 at the time of this writing , but as you can see in the console dump, the -v flag is used instead of the --volume-from, as if the plugin did not detect it was running inside a container . *Steps to reproduce** Copy [this gist|https://gist.github.com/PierreBtz/9bf58de96fdf5f0b0f272cba850f1161]* Set the executable permissions on the scripts.* Run the build script and then the run script.* The Jenkins instance will be available on port 8080. There is one job in it running the following:{noformat}node ('master') {sh 'pwd'img = docker.image('ubuntu')img.inside {sh 'pwd'}}{noformat}Do you think there is enough to reopen this issue?Thanks
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title
Pierre Beitz commented on JENKINS-33632
Re: docker.inside broken
Hello Jesse Glick, I think I found a self-contained example showing that the issue is still around. Using the following versions of Docker
Docker 1.12.2, build bb80604 (on linux).
Docker 1.12.3, build 6b644ec, experimental (on windows).
And using this gist, I ended up with the following error on my two machines:
$ docker run -t -d -u 1000:1000 -w /var/jenkins_home/jobs/demo/workspace -v /var/jenkins_home/jobs/demo/workspace:/var/jenkins_home/jobs/demo/workspace:rw -v /var/jenkins_home/jobs/demo/workspace@tmp:/var/jenkins_home/jobs/demo/workspace@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e -e --entrypoint cat ubuntu
[Pipeline] {
[Pipeline] sh
[workspace] Running shell script
sh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/pid: Directory nonexistent
sh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-log.txt: Directory nonexistent
sh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-result.txt: Directory nonexistent
Version of the Docker pipeline is 1.9.1 at the time of this writing. Steps to reproduce
Copy this gist
Set the executable permissions on the scripts.
Run the build script and then the run script.
The Jenkins instance will be available on port 8080. There is one job in it running the following:
node ('master') {
sh 'pwd'
img = docker.image('ubuntu')
img.inside {
sh 'pwd'
}
}
Do you think there is enough to reopen this issue? Thanks
Add Comment
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title Jesse Glick resolved as Incomplete Version 1.9 had a related fix. Please do not reopen without complete, self-contained steps to reproduce from scratch. Jenkins / JENKINS-33632 docker.inside broken Change By: Jesse Glick Status: Reopened Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title Danny Waite commented on JENKINS-33632 Re: docker.inside broken Spoke too soon, this example does not work: https://github.com/danny-waite/gceme Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Danny Waite commented on JENKINS-33632 Re: docker.inside broken This very simple project (derived from Google's Jenkins/Kubernetes example) appears to be working: https://github.com/danny-waite/jenkins-sample-pipeline-app Great work, many thanks, will continue to more detailed testing, I realise this isn't done 'by the book', ie. the use of `sh` blocks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Christopher Eck commented on JENKINS-33632 Re: docker.inside broken Nice! Looking forward to trying it out. Is there a timeline for the next release? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Jesse Glick commented on JENKINS-33632 Re: docker.inside broken Christopher Eck if that is the only issue, then PR 56 might have fixed it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Christopher Eck commented on JENKINS-33632 Re: docker.inside broken Jesse, the problem seems to be that the plugin isn't issuing --volumes-from in this case. It's still attempting to use -v. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Jesse Glick commented on JENKINS-33632 Re: docker.inside broken A recent release allows inside to work when the node is also running in a container, using --volumes-from. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33632 docker.inside broken Change By: Jesse Glick Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Danny Waite commented on JENKINS-33632 Re: docker.inside broken Guys, I'm also seeing this issue when running on Kubernetes as outlined in the following article https://cloud.google.com/solutions/configuring-jenkins-container-engine Any help appreciated, as Christopher mentioned this is a blocking issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Christopher Eck commented on JENKINS-33632 Re: docker.inside broken In my environment, we're running the jenkins master and slaves as containers within kubernetes. I'm passing /var/run/docker.sock into each slave container so it connects to the local host's docker daemon. On a slave, I'm attempting to run docker.inside on a newly built container and seeing this behavior. I expect, based on what I read of the demo, that this should work properly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Jacob Blain Christen commented on JENKINS-33632 Re: docker.inside broken Joost Meijles, docker.inside only works with a local docker-host. This means that if the docker daemon that you've specified via withServer is not actually local (typically this means that the Jenkins slave and Docker daemon share the same PID namespace) to the Jenkins executor process, it simply will not work. This is because docker.inside bind-mounts in the workspace which of course relies on the workspace filesystem existing on the same system as the docker daemon. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Vitor Dantas commented on JENKINS-33632 Re: docker.inside broken I reported a similar issue JENKINS-37069, only difference is the message when trying to access the durable folder is "Permission denied" on my setup instead of "Directory nonexistent". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Gavin Stringfellow reopened an issue Jenkins / JENKINS-33632 docker.inside broken Change By: Gavin Stringfellow Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Christopher Eck edited a comment on JENKINS-33632 Re: docker.inside broken Also seeing this issue - blocking us from migrating our build to Jenkins.I expect we're supposed to be seeing --volumes-from instead of -vJenkins: 2.17Docker: 1.10.3The demo doesn't mount /var/lib/jenkins or any other host path into the jenkins host container, and it doesn't appear to use slave containers to run the workflow steps, so I'm not sure how this works in the demo case either... I'd like to reopen this issue as it doesn't appear to be working properly and there are no good docs that I can find on how to set up the Jenkins master and slave containers. I'll give it a day or two and re-open if I don't hear anything. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Christopher Eck edited a comment on JENKINS-33632 Re: docker.inside broken Also seeing this issue - blocking us from migrating our build to Jenkins.I expect we're supposed to be seeing --volumes-from instead of -vJenkins: 2.17Docker: 1.10.3 The demo doesn't mount /var/lib/jenkins or any other host path into the jenkins host container, and it doesn't appear to use slave containers to run the workflow steps, so I'm not sure how this works in the demo case either... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title Christopher Eck commented on JENKINS-33632 Re: docker.inside broken Also seeing this issue - blocking us from migrating our build to Jenkins. I expect we're supposed to be seeing --volumes-from instead of -v Jenkins: 2.17 Docker: 1.10.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33632) docker.inside broken
Title: Message Title
Joost Meijles commented on JENKINS-33632
Re: docker.inside broken
Getting the same issues with v2.7 (and Docker v1.11) as well. The following code, from the docker-workflow-plugin flow.groovy script:
node {
docker.withServer('10.57.3.192:2375')
{
def maven = docker.image('maven:3.3.9-jdk-8');
maven.inside {
sh "echo paard"
}
}
}
gives:
Running on master in /var/jenkins_home/workspace/test
[Pipeline] {
[Pipeline] withDockerServer
[Pipeline] {
[Pipeline] sh
[test] Running shell script
+ docker inspect -f . maven:3.3.9-jdk-8
.
[Pipeline] withDockerContainer
$ docker run -t -d -u 1000:1000 -w /var/jenkins_home/workspace/test -v /var/jenkins_home/workspace/test:/var/jenkins_home/workspace/test:rw -v /var/jenkins_home/workspace/test@tmp:/var/jenkins_home/workspace/test@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e maven:3.3.9-jdk-8 cat
[Pipeline] {
[Pipeline] sh
[test] Running shell script
sh: 1: cannot create /var/jenkins_home/workspace/test@tmp/durable-b6571b6c/pid: Directory nonexistent
sh: 1: cannot create /var/jenkins_home/workspace/test@tmp/durable-b6571b6c/jenkins-log.txt: Directory nonexistent
sh: 1: cannot create /var/jenkins_home/workspace/test@tmp/durable-b6571b6c/jenkins-result.txt: Directory nonexistent
[Pipeline] }
$ docker stop 1ec4e5fe48cb461e14b2ca6facccfa1ee94feff74c82045939a4c6dc16368027
$ docker rm -f 1ec4e5fe48cb461e14b2ca6facccfa1ee94feff74c82045939a4c6dc16368027
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // withDockerServer
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code -2
Finished: FAILURE
Should this issue be reopened? Or am I missing something in the setup?
Add Comment
