[JIRA] (JENKINS-35217) docker.inside broken
Title: Message Title Jesse Glick commented on JENKINS-35217 Re: docker.inside broken Have not tried specifically with the Docker plugin, but works fine with manually attached JNLP agents running inside a container. 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-35217) docker.inside broken
Title: Message Title sébastien glon commented on JENKINS-35217 Re: docker.inside broken This work only for me if i set this "/home/jenkins" line on volumes on Jenkins admin Docker template. If i not set but volume /home/jenkins is defined on Image, this not work. Is it possible to auto add "Remote Filing System Root" param on volumes? 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-35217) docker.inside broken
Title: Message Title Jesse Glick commented on JENKINS-35217 Re: docker.inside broken the best way to achive this is to add volume-from with jenkins-slave container in docker step This already happens automatically when Jenkins can determine that the agent is running inside a container. 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-35217) docker.inside broken
Title: Message Title sébastien glon commented on JENKINS-35217 Re: docker.inside broken If i externalize my /home/jenkins/workspace to my host, Jenkins docker step can mount host folder on new container and this work. But this is not safe because all container can see all workspace. I think the best way to achive this is to add volume-from with jenkins-slave container in docker step 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-35217) docker.inside broken
Title: Message Title Gavin Stringfellow commented on JENKINS-35217 Re: docker.inside broken How did you remove the '-u 1000:1000'? I am running into the same problem. 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-35217) docker.inside broken
Title: Message Title sébastien glon commented on JENKINS-35217 Re: docker.inside broken For me this is do to -u1000:1000 that is not supproted by golang image and many other. 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.
