[JIRA] (JENKINS-56888) Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Title: Message Title Andy Taylor commented on JENKINS-56888 Re: Unexpected cgroup syntax when using docker-in-docker slave launched via SSH This bug is causing us a lot of pain - is there any chance someone could review and merge the fix provided by Evan please?! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198559.1554406573000.8459.1580328720145%40Atlassian.JIRA.
[JIRA] (JENKINS-56888) Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Title: Message Title Andy Taylor assigned an issue to Andy Taylor Jenkins / JENKINS-56888 Unexpected cgroup syntax when using docker-in-docker slave launched via SSH Change By: Andy Taylor Assignee: Andy Taylor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198559.1554406573000.8455.1580328660452%40Atlassian.JIRA.
[JIRA] (JENKINS-56888) Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Title: Message Title
pjdarton updated an issue
Jenkins / JENKINS-56888
Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Change By:
pjdarton
In our configuration, we use the Docker -Workflow plugin as a build cloud to dynamically spawn Jenkins slaves ([https:// wiki plugins .jenkins.io/ display/JENKINS/Docker+Plugin] docker-workflow) . ] In some cases, we need a sandboxed docker environment for building images, so the slaves start a docker-in-docker daemon when they're launched. The slaves are connected via SSH using the Docker plugin's normal "Connect with SSH" launch method. The result is that the default `agent` environment is a remote slave connected via SSH that's running in a docker container. The slave has a docker client installed, and the default docker host is the docker-in-docker daemon running within the slave container.When using the dockerfile type of agent parameter ([https://jenkins.io/doc/book/pipeline/syntax/#agent-parameters]), the {{ withDockerContainer }} step fails with error message: {noformat}java.io.IOException: Unexpected cgroup syntax /docker/a913fc1766a972d99ae545d6ba2508fe797c2df9b6371ff0be629436a30502a4/docker/a913fc1766a972d99ae545d6ba2508fe797c2df9b6371ff0be629436a30502a4/user/jenkins/0at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60)at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45)at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37)at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336)at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159)at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268)at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176)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(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:134)at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66)at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:122)at
[JIRA] (JENKINS-56888) Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Title: Message Title Evan Bluhm commented on JENKINS-56888 Re: Unexpected cgroup syntax when using docker-in-docker slave launched via SSH I've opened https://github.com/jenkinsci/docker-workflow-plugin/pull/169 as a potential fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56888) Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Title: Message Title
Evan Bluhm updated an issue
Jenkins / JENKINS-56888
Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Change By:
Evan Bluhm
In our configuration, we use the Docker plugin as a build cloud to dynamically spawn Jenkins slaves ( [ https://wiki.jenkins.io/display/JENKINS/Docker+Plugin ] . In some cases, we need a sandboxed docker environment for building images, so the slaves start a docker-in-docker daemon when they're launched. The slaves are connected via SSH using the Docker plugin's normal "Connect with SSH" launch method. The result is that the default `agent` environment is a remote slave connected via SSH that's running in a docker container. The slave has a docker client installed, and the default docker host is the docker-in-docker daemon running within the slave container. When using the dockerfile type of agent parameter ( [ https://jenkins.io/doc/book/pipeline/syntax/#agent-parameters ] ), the withDockerContainer step fails with error message: { { noformat} java.io.IOException: Unexpected cgroup syntax /docker/a913fc1766a972d99ae545d6ba2508fe797c2df9b6371ff0be629436a30502a4/docker/a913fc1766a972d99ae545d6ba2508fe797c2df9b6371ff0be629436a30502a4/user/jenkins/0 }} {{ at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60) }} {{ at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45) }} {{ at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37) }} {{ at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336) }} {{ at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) }} {{ 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(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:134) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:122) }} {{ at
[JIRA] (JENKINS-56888) Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Title: Message Title Evan Bluhm created an issue Jenkins / JENKINS-56888 Unexpected cgroup syntax when using docker-in-docker slave launched via SSH Issue Type: Bug Assignee: Unassigned Components: docker-workflow-plugin Created: 2019-04-04 19:36 Environment: Operating System: Docker 17.09.0-ce on Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-127-generic x86_64) Java Runtime: OpenJDK Runtime Environment 1.8.0_181-8u181-b13-2~deb9u1-b13 How Jenkins was installed: docker run -v /jenkins-data-mount:/var/jenkins_home jenkins/jenkins:lts Jenkins + Plugin Versions: Jenkins: 2.164.1 docker-workflow: 1.18 docker-plugin: 1.1.6 docker-java-api: 3.0.14 docker-commons: 1.14 ssh-slaves: 1.29.4 Reverse proxy: None Slave nodes: Launching nodes using the Docker plugin via the SSH connection method (https://wiki.jenkins.io/display/JENKINS/Docker+Plugin). More info in the description Priority: Minor Reporter: Evan Bluhm In our configuration, we use the Docker plugin as a build cloud to dynamically spawn Jenkins slaves (https://wiki.jenkins.io/display/JENKINS/Docker+Plugin. In some cases, we need a sandboxed docker environment for building images, so the slaves start a docker-in-docker daemon when they're launched. The slaves are connected via SSH using the Docker plugin's normal "Connect with SSH" launch method. The result is that the default `agent` environment is a remote slave connected via SSH that's running in a docker container. The slave has a docker client installed, and the default docker host is the docker-in-docker daemon running within the slave container. When using the dockerfile type of agent parameter (https://jenkins.io/doc/book/pipeline/syntax/#agent-parameters), the withDockerContainer step fails with error message: java.io.IOException:
