[JIRA] (JENKINS-58668) Doesn't create a file within docker.inside {}

[jbal...@edgelab.ch (JIRA)]

Title: Message Title

Jonathan Ballet created an issue   Jenkins / JENKINS-58668 Doesn't create a file within docker.inside {} Issue Type: Bug Assignee: Dominik Bartholdi Components: config-file-provider-plugin Created: 2019-07-26 08:18 Environment: jenkins: 2.187 config-file-provider-plugin: 3.6.2 docker-pipeline: 1.18 Labels: config-file-provider docker Priority: Major Reporter: Jonathan Ballet Using a `configFileProvider` within a `docker.inside {}` code block doesn't create the configuration file *in* the container but on *the host* running the container. node { docker.image('alpine').inside { configFileProvider([configFile(fileId: 'test-123', targetLocation: '/foobar')]) { sh "cat /foobar" } } } Produces the following output: [Pipeline] Start of Pipeline [Pipeline] node Running on qemu2 in /home/jenkins/workspace/t-jenkins_bug-config-file-docker [Pipeline] { [Pipeline] withDockerServer [Pipeline] { [Pipeline] sh + docker inspect -f . alpine . [Pipeline] withDockerContainer qemu2 does not seem to be running inside a container $ docker run -t -d -u 0:0 -w /home/jenkins/workspace/t-jenkins_bug-config-file-docker -v /home/jenkins/workspace/t-jenkins_bug-config-file-docker:/home/jenkins/workspace/t-jenkins_bug-config-file-docker:rw,z -v /home/jenkins/workspace/t-jenkins_bug-config-file-docker@tmp:/home/jenkins/workspace/t-jenkins_bug-config-file-docker@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** alpine cat $ docker top e4288736bfaaa9adb71e175384021ae505f1cab767b3ef4219783097b57ffb81 -eo pid,comm [Pipeline] { [Pipeline] configFileProvider provisioning config files... copy managed file [MyCustom] to file:/foobar [Pipeline] { [Pipeline] echo In the container [Pipeline] sh + cat /foobar cat: can't open '/foobar': No such file or directory [Pipeline] echo hudson.AbortException: script returned exit code 1 [Pipeline] } [Pipeline] // configFileProvider [Pipeline] } $ docker stop --time=1 e4288736bfaaa9adb71e175384021ae505f1cab767b3ef4219783097b57ffb81 $ docker rm -f e4288736bfaaa9adb71e175384021ae505f1cab767b3ef4219783097b57ffb81 [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // withDockerServer [Pipeline] echo On the container [Pipeline] sh + cat /foobar 123 456[Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline (I have an additional withDockerServer around in this example, and Jenkins connects as root on the Docker host machine.) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200950.1564129139000.1564.1564129200237%40Atlassian.JIRA.