-
Bug
-
Resolution: Duplicate
-
Minor
-
Jenkins 2.6
Image.inside automatically sets up volumes and a workdir. Its impossible to override this workdir. Ideally workdir should not be touched at all IMO but at the very least it should be overridable.
When using a command like this:
build.inside('-w /usr/src/app/') { sh 'npm run lint' }
You'll get output like this
[Pipeline] withDockerContainer $ docker run -t -d -u 1002:1002 -w /usr/src/app/ -w /home/*******/workspace/*******/development -v /home/*******/workspace/*******/development:/home/*******/workspace/*******/development:rw -v /home/*******/workspace/*******/development@tmp:/home/*******/workspace/*******/development@tmp:rw -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** *******:5000/*******/*******:11-feature
You can see that the `-w` option is passed to the command but since the plugin forces `-w` /path/to/jenkins/workspace no matter what their is no way around this outside `cd /workdir` inside every inside command.
- duplicates
-
-
- Resolved
-
- relates to
-
JENKINS-61743 Customizable workspace and working directory of docker.images.inside()
-
- Open
-
[JENKINS-35406] Image.inside overrides working directory
Coleman
created issue -
Coleman
made changes -
| Description |
Original:
Image.inside automatically sets up volumes and a workdir. Its impossible to override this workdir. Ideally workdir should not be touched at all IMO but at the very least it should be overridable. When using a command like this: {code} build.inside('-w /usr/src/app/') { sh 'npm run lint' } {code} You'll get output like this {code} [Pipeline] withDockerContainer $ docker run -t -d -u 1002:1002 -w /usr/src/app/ -w /home/*******/workspace/*******/development -v /home/*******/workspace/*******/development:/home/*******/workspace/*******/development:rw -v /home/*******/workspace/*******/development@tmp:/home/*******/workspace/*******/development@tmp:rw -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** *******:5000/*******/*******:11-feature {code} You can see that the `-w` option is passed to the command but since the plugin forces `-w` /path/to/jenkins/workspace no matter what their is no way around this outside `cd /workdir` inside every inside command. |
New:
Image.inside automatically sets up volumes and a workdir. Its impossible to override this workdir. Ideally workdir should not be touched at all IMO but at the very least it should be overridable. When using a command like this: {code} build.inside('-w /usr/src/app/') { sh 'npm run lint' } {code} You'll get output like this {code} [Pipeline] withDockerContainer $ docker run -t -d -u 1002:1002 -w /usr/src/app/ -w /home/*******/workspace/*******/development -v /home/*******/workspace/*******/development:/home/*******/workspace/*******/development:rw -v /home/*******/workspace/*******/development@tmp:/home/*******/workspace/*******/development@tmp:rw -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** *******:5000/*******/*******:11-feature {code} You can see that the `-w` option is passed to the command but since the plugin forces `-w` /path/to/jenkins/workspace no matter what their is no way around this outside `cd /workdir` inside every inside command. |
| Link |
New:
This issue duplicates |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Workflow | Original: JNJira [ 171700 ] | New: JNJira + In-Review [ 199153 ] |
| Labels | Original: workflow | New: pipeline workflow |
| Labels | Original: pipeline workflow | New: pipeline |
Sadly, it seems this issues still exists. I'm proposing to re-open it that is is addresses. It remains unclear, why this is enforced. Docker allows nicely isolating this from any host environment, so why does Jenkins (or the plugin) insist on bringing thing knowledge in?
I agree, this is still a problem: for me, it breaks parallel stages unstash-ing the same Python venv (which isn't supposed to be moved, for some reason) at different container-paths.
(I'm doing agent { docker
{ ... }} in a declarative pipeline, which I assume uses the same implementation?)
That one is still open: JENKINS-61743
Raphael
added a comment - - edited I agree, this is still a problem: for me, it breaks parallel stages unstash -ing the same Python venv (which isn't supposed to be moved, for some reason) at different container-paths.
(I'm doing agent { docker
{ ... }
} in a declarative pipeline, which I assume uses the same implementation?)
That one is still open: JENKINS-61743
You would use
JENKINS-33510, if that worked. For now, use cd.