blocks|key|655664|text|有一次我遇到了类似的问题，问题不是工作目录，因为我使用ENV变量从任何地方访问我的二进制文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|655665|我的问题是权限问题，尽管我没有看到任何关于权限的错误消息。只需以root用户身份执行命令并查看是否有效，例如：|655666|pipeline+{
++agent+{
++++docker+{
++++++image+'jekyll/jekyll:builder'
++++++args+'-v+$HOME:/srv/jekyll+-w+/srv/jekyll+-u+root'
++++}
++}
++stages+{
++++stage('Test')+{
++++++steps+{
++++++sh+'cd+/srv/jekyll+&&+ls+-l'
++++++}
++++}
++}
}|code-block|syntax|javascript|655667|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had a similar issue once, the problem was not the working directory, as I was using ENV variables to access my binaries from anywhere.

My issue was a permissions issue, even though I did not see any error message regarding permissions. Simply execute the command as the root user and see if that works , e.g. :

<pre><code>pipeline {
 agent {
 docker {
 image 'jekyll/jekyll:builder'
 args '-v $HOME:/srv/jekyll -w /srv/jekyll -u root'
 }
 }
 stages {
 stage('Test') {
 steps {
 sh 'cd /srv/jekyll &amp;&amp; ls -l'
 }
 }
 }
}
</code></pre>

blocks|key|655658|text|@Nagri不幸的是，我仍然不能指定工作目录和卷映射。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|655659|但我可以以root身份运行jekylll。|655660|这并不理想，但至少它是有效的。|655661|++++pipeline+{
++++++++agent+{
++++++++++++docker+{
++++++++++++++++image+'jekyll/jekyll:builder'
++++++++++++++++args+'-u+root'
++++++++++++}
++++++++}
++++++++stages+{
++++++++++++stage('Test')+{
++++++++++++++++steps+{
++++++++++++++++++++sh+'mkdir+-p+_site'
++++++++++++++++++++sh+'jekyll+build'
++++++++++++++++}
++++++++++++}
++++++++}
++++}|code-block|syntax|javascript|655662|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

@Nagri unfortunately I could still not specify the working directory and volume mapping.
But I could run jekylll as root.
It is not ideal but at least it works.
<pre><code>
 pipeline {
 agent {
 docker {
 image 'jekyll/jekyll:builder'
 args '-u root'
 }
 }
 stages {
 stage('Test') {
 steps {
 sh 'mkdir -p _site'
 sh 'jekyll build'
 }
 }
 }
 }

</code></pre>

blocks|key|655653|text|您可以结合使用docker+{}和dir+{}来控制工作目录：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|655654|pipeline+{
++agent+{
++++docker+{
++++++image+'jekyll/jekyll:builder'
++++++args+'-v+$HOME:/srv/jekyll'
++++}
++}
++stages+{
++++stage('Test')+{
++++++steps+{
++++++++dir(path:+'/srv/jekyll')+{
++++++++++sh+'ls+-l'
++++++++}
++++++}
++++}
++}
}|code-block|syntax|javascript|655655|我放弃了-w参数，因为它没有效果，并用dir(path:+'/srv/jekyll'){...}替换了cd+/src/jekyll|655656|entityMap^0|7|9|H|6|0|0|4|2|J|T|1F|E|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$]]

You can combine <code>docker {}</code> with <code>dir {}</code> to control the working directory:

<pre><code>pipeline {
 agent {
 docker {
 image 'jekyll/jekyll:builder'
 args '-v $HOME:/srv/jekyll'
 }
 }
 stages {
 stage('Test') {
 steps {
 dir(path: '/srv/jekyll') {
 sh 'ls -l'
 }
 }
 }
 }
}
</code></pre>

I've dropped the <code>-w</code> argument, since it has no effect, and replaced <code>cd /src/jekyll</code> with <code>dir(path: '/srv/jekyll'){...}</code>

blocks|key|699352|text|我们有一个相同的要求，使用不同于容器中默认工作目录的工作目录，在检查之后，它被理解为现在是不可能的。有关更多详细信息，请查看此处JENKINS-41474、JENKINS-35406、JENKINS-33510|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|699353|另一种方法是使用dir("path_to_work")+{+sh+'+'}，但它也不起作用。因此，唯一的方法是使用args将卷挂载到容器中，并使用其中的更改目录命令运行所有命令|style|CODE|699354|++pipeline+{
++agent+{
++++docker+{
++++++image+'alpine:3.7'
++++++args+'-v+$HOME/src:/src'
++++}
++}
++stages+{
++++stage('Build')+{
++++++steps+{
++++++sh+'cd+/src+;+./run_build.sh'
++++++}
++++}
++}
}|code-block|syntax|javascript|699355|entityMap|0|LINK|mutability|MUTABLE|url|https://issues.jenkins-ci.org/browse/JENKINS-41474|1|https://issues.jenkins-ci.org/browse/JENKINS-35406|2|https://issues.jenkins-ci.org/browse/JENKINS-33510^0|1S|D|0|26|D|1|2K|D|2|0|8|T|1L|4|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]|$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@$A|19|B|1A|F|G]|$A|1B|B|1C|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1D|8|@]|9|@]|C|$K|L]]|$1|M|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]|W|$5|P|Q|R|C|$S|X]]]]

we had a same requirement to use work directory different than the default one in container, after checking it understood as of now its not possible. check here for more details <a href="https://issues.jenkins-ci.org/browse/JENKINS-41474" rel="nofollow noreferrer">JENKINS-41474</a>, <a href="https://issues.jenkins-ci.org/browse/JENKINS-35406" rel="nofollow noreferrer">JENKINS-35406</a>, <a href="https://issues.jenkins-ci.org/browse/JENKINS-33510" rel="nofollow noreferrer">JENKINS-33510</a>

the other way is to use <code>dir("path_to_work") { sh ' '}</code>, but it did not worked either.
so only way is to mount the volume in container with <code>args</code> and run all the commands with change directory command in it

<pre><code> pipeline {
 agent {
 docker {
 image 'alpine:3.7'
 args '-v $HOME/src:/src'
 }
 }
 stages {
 stage('Build') {
 steps {
 sh 'cd /src ; ./run_build.sh'
 }
 }
 }
}
</code></pre>

blocks|key|699357|text|我找到的解决方案不是尝试手动设置目录，因为我希望并行执行同一管道的多个实例，而是避免节点重用。https://www.jenkins.io/doc/book/pipeline/docker/#workspace-synchronization|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|699358|pipeline+{
++++agent+{
++++++++docker+{
++++++++++++//+parent+image:+https://hub.docker.com/layers/maven/library/maven/3.6.3-jdk-11/images/sha256-1801d353e27e68d60355b371ddfd2ed8d06204bc3266f1746fdade897bb8b6bd?context=explore
++++++++++++image+'fra.ocir.io/XXX/maven:3.6.3-jdk-11'
++++++++++++registryUrl+'https://fra.ocir.io/'
++++++++++++registryCredentialsId+'YYY'
++++++++++++args+'-v+/var/run/docker.sock:/var/run/docker.sock+-v+/opt/data/jenkins/.m2/settings.xml:/usr/share/maven/conf/settings.xml'

++++++++++++//+Create+a+new+tmp+folder+for+the+current+build
++++++++++++reuseNode+false
++++++++}
++++}
++++environment+{
++++++++JAVA_HOME+=+'/usr/local/openjdk-11'
++++}
++++stages+{
++++++++stage('Build+Test')+{
++++++++++++steps+{
++++++++++++++++//+https://www.jenkins.io/doc/pipeline/steps/git/
++++++++++++++++git+credentialsId:+'credentials-jenkins-gitlab',
++++++++++++++++++++url:+'git@####.git',
++++++++++++++++++++branch:+'develop-devops'

++++++++++++++++//+https://plugins.jenkins.io/pipeline-maven/
++++++++++++++++withMaven(
++++++++++++++++++++maven:+'maven-3.6.3',
++++++++++++++++++++jdk:+'jdk-11'
++++++++++++++++){
++++++++++++++++++++sh+'printenv+%7Csort'

++++++++++++++++++++sh+'mvn+help:effective-settings'

++++++++++++++++++++sh+'mvn+verify'

++++++++++++++++++++sh+'echo+"$(date)"+>>+test-file'
++++++++++++++++}
++++++++++++}
++++++++}
++++}
++++post+{
++++++++++++success+{
++++++++++++++++//+Check+if+the+file+is+dirty+with+previous+writes
++++++++++++++++sh+'cat+test-file'

++++++++++++++++//+Clean+the+current+workspace
++++++++++++++++cleanWs()
++++++++++++}
++++++++}
}|code-block|syntax|javascript|699359|entityMap|0|LINK|mutability|MUTABLE|url|https://www.jenkins.io/doc/book/pipeline/docker/#workspace-synchronization^0|1B|22|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

The solution I've found is not to try to set up the directory manually, since I want to execute multiple instances of the same pipeline in parallel, but to avoid node re-utilization.
<a href="https://www.jenkins.io/doc/book/pipeline/docker/#workspace-synchronization" rel="nofollow noreferrer">https://www.jenkins.io/doc/book/pipeline/docker/#workspace-synchronization</a>
<pre class="lang-sh prettyprint-override"><code>pipeline {
 agent {
 docker {
 // parent image: https://hub.docker.com/layers/maven/library/maven/3.6.3-jdk-11/images/sha256-1801d353e27e68d60355b371ddfd2ed8d06204bc3266f1746fdade897bb8b6bd?context=explore
 image 'fra.ocir.io/XXX/maven:3.6.3-jdk-11'
 registryUrl 'https://fra.ocir.io/'
 registryCredentialsId 'YYY'
 args '-v /var/run/docker.sock:/var/run/docker.sock -v /opt/data/jenkins/.m2/settings.xml:/usr/share/maven/conf/settings.xml'

 // Create a new tmp folder for the current build
 reuseNode false
 }
 }
 environment {
 JAVA_HOME = '/usr/local/openjdk-11'
 }
 stages {
 stage('Build Test') {
 steps {
 // https://www.jenkins.io/doc/pipeline/steps/git/
 git credentialsId: 'credentials-jenkins-gitlab',
 url: 'git@####.git',
 branch: 'develop-devops'

 // https://plugins.jenkins.io/pipeline-maven/
 withMaven(
 maven: 'maven-3.6.3',
 jdk: 'jdk-11'
 ){
 sh 'printenv |sort'

 sh 'mvn help:effective-settings'

 sh 'mvn verify'

 sh 'echo &quot;$(date)&quot; &gt;&gt; test-file'
 }
 }
 }
 }
 post {
 success {
 // Check if the file is dirty with previous writes
 sh 'cat test-file'

 // Clean the current workspace
 cleanWs()
 }
 }
}
</code></pre>

I have noticed when using Jenkins with the Docker Pipeline plugin. When I create a Jenkins file to run commands in a docker container that it always creates a volume mapping of the Jenkins workspace directory mapped to the same path in the running container. It also creates a working directory with the same path.

<pre><code>docker run -t -d -u 127:134 -w /var/lib/jenkins/workspace/DockerTest 
-v /var/lib/jenkins/workspace/DockerTest:/var/lib/jenkins/workspace/DockerTest:rw,z 
-v /var/lib/jenkins/workspace/DockerTest@tmp:/var/lib/jenkins/workspace/DockerTest@tmp:rw,z 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
jekyll/jekyll:builder cat
</code></pre>

I tried to override this by providing arguments in my Jenkinsfile for Docker like this:

<pre><code>pipeline {
 agent {
 docker {
 image 'jekyll/jekyll:builder'
 args '-v $HOME:/srv/jekyll -w /srv/jekyll'
 }
 }
 stages {
 stage('Test') {
 steps {
 sh 'cd /srv/jekyll &amp;&amp; ls -l'
 }
 }
 }
}
</code></pre>

It seems that this just prepends the options to the Docker command and the workdir and volume mapping gets overwritten by the default settings:

<pre><code>docker run -t -d -u 127:134 
-v $HOME:/srv/jekyll 
-w /srv/jekyll 
-w /var/lib/jenkins/workspace/DockerTest 
-v /var/lib/jenkins/workspace/DockerTest:/var/lib/jenkins/workspace/DockerTest:rw,z 
-v /var/lib/jenkins/workspace/DockerTest@tmp:/var/lib/jenkins/workspace/DockerTest@tmp:rw,z 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
-e ******** 
jekyll/jekyll:builder cat
</code></pre>

Is there any way that I can override the volume mappings and working directory in any way?

Jenkins Docker Pipeline override working directory

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在使用Jenkins和Docker Pipeline插件时，我注意到了这一点。当我创建一个Jenkins文件来在docker容器中运行命令时，它总是创建Jenkins工作区目录的卷映射，映射到运行容器中的相同路径。它还会创建一个具有相同路径的工作目录。docker run -t -d -u 127:134 -w /va...

问Jenkins Docker管道覆盖工作目录
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins Docker管道覆盖工作目录EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins Docker管道覆盖工作目录
EN