I have worked it around by using `withDockerContainer` step.

stage('change directory') {
    steps {
        dir('new-dir') {
            withDockerContainer(image: 'my-image') {
                sh 'pwd'
            }
        }
    }
 }

Basically you use dir to change directory before launching the container, and the when booting up a container, the current path will be made the working directory inside the container.
 

I haven't tested Michael Wu's work-around, but regardless, it's still a work-around – it is not a fix.

Should fix the bug so that It works as documented (preferred) or update documentation with the work-around.

I'd like to see this too. Currently, I'm running every one of my sh commands like this:

```

sh "cd dir && command"

sh "cd dir && othercommand"

```

As you can see, this is quite annoying. It would be great if I could just surround it by a `dir` block and have it just, work.

Logs:

Docker version is older than 17.12, working directory will be /var/jenkins_home/workspace/gsilva-pro_master-FNQGFOZNCGYYR7K4UGJOX5A6UTRZHRZ2ZIJHDRTUJOUALWVMZQJA not /var/jenkins_home/workspace/gsilva-pro_master-FNQGFOZNCGYYR7K4UGJOX5A6UTRZHRZ2ZIJHDRTUJOUALWVMZQJA/web-ui

Output of docker version:

Docker version 17.12.0-ce, build c97c6d6

Host ubuntu server 16.04 LTS

Jenkins Blue Ocean running as a docker container version:

1.4.1  · Core 2.89.3  · 61988a2

This is a annoying specially because my repository has multprojects Angular and Java, and I need to change directory for start the builds.

Maybe the code that checks for version has a bug, that do not parse 17.12.0-ce

Or maybe the container jenkis has no access to docker. But I'm running with docker.sock mapped correctly

dir never worked in declarative pipelines. I didn't try in scripted pipeline. I do like Christopher, I prefix my commands with "cd my-directory &&" and it's not sexy at all to see this in the Blue Ocean UI

Any updates or solution to this issue

Docker version is older than 17.12, working directory will be /var/jenkins_home/workspace/gsilva-pro_master-FNQGFOZNCGYYR7K4UGJOX5A6UTRZHRZ2ZIJHDRTUJOUALWVMZQJA not /var/jenkins_home/workspace/gsilva-pro_master-FNQGFOZNCGYYR7K4UGJOX5A6UTRZHRZ2ZIJHDRTUJOUALWVMZQJA/web-ui

burtsevyg what do you expect from me by assigning me to this ticket?

I was able to fix the issue by applying the following patch to https://github.com/jenkinsci/docker-workflow-plugin, building the .hpi w/mvn, and placing it into my Jenkins server.

diff --git a/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java b/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java
index 862b454..efcb6b2 100644
--- a/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java
+++ b/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java
@@ -255 +255,2 @@ public class WithContainerStep extends AbstractStepImpl {
-                                    launcher.getListener().getLogger().println("Docker version is older than 17.12, working directory will be " + ws + " not " + path);
+                                    String safePath = path.replace("'", "'\"'\"'");
+                                    starter.cmds().addAll(0, Arrays.asList("sh", "-c", "cd '" + safePath + "'; \"$@\"", "--"));

mslattery Is your fix merged into master then? Can you point me to a PR if there is one?

imdahmd - https://github.com/jenkinsci/docker-workflow-plugin/pull/156

I have unassigned the ticket, because I am not the plugin maintainer. The pull request looks good to me tho

A fix for this issue was just released in Docker Pipeline Plugin version 1.19.