[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()

[martric...@web.de (JIRA)]

Title: Message Title

Mart Rich created an issue   Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Issue Type: New Feature Assignee: Unassigned Attachments: example.txt, proposal.txt Components: docker-workflow-plugin Created: 2020-03-30 15:19 Priority: Major Reporter: Mart Rich Hello, I want to have a possibility to change the "workdir" & "volume" destination directory within the image which will be started by the "docker.image.inside"-command. The current problem is that the path to the mount-destination within the container and the working directory are hard-coded: Hard-coded volumes: https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L193 https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L194 Hard-coded Work-Dir (parameter 4 is always "ws" == "workspace"): https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L198 So the "default" image.inside command (on windows) results in something like: docker run -t -d -w ${WORKSPACE} -v ${WORKSPACE}:${WORKSPACE} -v ${WORKSPACE}@tmp:${WORKSPACE}@tmp It's not "clean" because the destination in the started container is hardcoded as the same directory of the workspace. This can cause issues with rights, existing drives, and other stuff. Feature-Request in short: I want to have the possibility to change the working directory and the volume mounting directory which points into the started container. The default behavior can be kept as it is I have two proposals (from the user side of view) attached in (proposal.txt)     Background how I ran into this: My System is a Jenkins-Master on a Linux-Server. I have two Slaves one Linux & one Windows. all this are real physical machines, no VM's or other stuff The Windows-Slave has a Windows-Server 2016 OS In my case the "workspace" of Jenkins is on the "E"-Drive. If you run the attached "example.txt" you can reproduce the error on every jenkins of course on my machine, dont need the "ws(...)" part The Error is an error on the docker run command because docker is unable to create a new Drive, as mounting point in the created container. I tried very much to create a "E"-Drive as volume in the Image, but I wasn't able to make it I tried symlinks, registry changes and stuff ... after all this I looked into the Code of the Plugin and thought this should be changeable ... All in all I think the origin of the problem are the hard-coded directories within the containers. Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205572.1585581551000.2999.1585581600160%40Atlassian.JIRA.