[JENKINS-74912] Jenkins docker-image plugin does not work with non-C windows drives

Type: Bug
Resolution: Unresolved
Priority: Minor
Component/s: docker-plugin, docker-workflow-plugin
Labels:
None

Similar Issues:
Powered by SuggestiMate

Show

If the workspace is on a different drive (in this case N) then docker.image fails with something like this:

docker.image('myregistry.com/myrepository/myimage:latest').inside {
    sh 'echo test'
}

00:00:07.112  $ docker run -d -t -w N:/myworkspace/myjob -v N:/myworkspace/myjob/:N:/myworkspace/myjob/ -v N:/myworkspace/myjob@tmp/:N:/myworkspace/myjob@tmp/ -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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** myregistry.com/myrepository/myimage:latest cmd.exe
. . .
00:00:08.850  java.io.IOException: Failed to run image 'myregistry.com/myrepository/myimage:latest'. Error: docker: Error response from daemon: hcs::CreateComputeSystem aa1593a84f9df2613191e56fa1b8037bd6d27a4b2c932a1b33e8b6e7f74961d0: The parameter is incorrect.

This is due to a limitation in docker on Windows:

Volumes on Windows-based containers: When using Windows-based containers, the destination of a volume inside the container must be one of:

a non-existing or empty directory
a drive other than C:

documentation and documentation

See https://github.com/moby/moby/issues/41681

The Jenkins docker-image plugin should be updated to either:
1) fail/warn in this case
2) provide a way to configure the mount
3) mount non-C paths to C inside the container. Any variables that reference the non-C drive may need to be updated to use the C drive

relates to

JENKINS-75102 Durable task plugin on Windows fails to run jenkins-wrapper.bat if workspace has a space

Resolved

JENKINS-75087 Provide way to disable mounting Jenkins workspace

Open

links to

Github #41681

Stack Overflow #63055516

Mark R created issue - 2024-11-22 22:25

Mark R made changes - 2024-11-22 22:25

Description

Original: If the workspace is on a different drive (in this case N) then docker.image fails with something like this:

{noformat}
00:00:07.112 $ docker run -d -t -w N:/myworkspace/myjob -v N:/myworkspace/myjob/:N:/myworkspace/myjob/ -v N:/myworkspace/myjob@tmp/:N:/myworkspace/myjob@tmp/ -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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** myregistry.com/myrepository/myimage:latest cmd.exe
. . .
00:00:08.850 java.io.IOException: Failed to run image 'myregistry.com/myrepository/myimage:latest'. Error: docker: Error response from daemon: hcs::CreateComputeSystem aa1593a84f9df2613191e56fa1b8037bd6d27a4b2c932a1b33e8b6e7f74961d0: The parameter is incorrect.
{noformat}

This is due to a limitation in docker on Windows:

{noformat}
Volumes on Windows-based containers: When using Windows-based containers, the destination of a volume inside the container must be one of:

a non-existing or empty directory
a drive other than C:
{noformat}

[documentation](https://docs.docker.com/reference/dockerfile/#notes-about-specifying-volumes)

See https://github.com/moby/moby/issues/41681

The Jenkins docker-image plugin should be updated to either:
1) fail/warn in this case
2) provide a way to configure the mount
3) mount non-C paths to C inside the container. Any variables that reference the non-C drive may need to be updated to use the C drive

New: If the workspace is on a different drive (in this case N) then docker.image fails with something like this:

{noformat}
00:00:07.112 $ docker run -d -t -w N:/myworkspace/myjob -v N:/myworkspace/myjob/:N:/myworkspace/myjob/ -v N:/myworkspace/myjob@tmp/:N:/myworkspace/myjob@tmp/ -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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** myregistry.com/myrepository/myimage:latest cmd.exe
. . .
00:00:08.850 java.io.IOException: Failed to run image 'myregistry.com/myrepository/myimage:latest'. Error: docker: Error response from daemon: hcs::CreateComputeSystem aa1593a84f9df2613191e56fa1b8037bd6d27a4b2c932a1b33e8b6e7f74961d0: The parameter is incorrect.
{noformat}

This is due to a limitation in docker on Windows:

{noformat}
Volumes on Windows-based containers: When using Windows-based containers, the destination of a volume inside the container must be one of:

a non-existing or empty directory
a drive other than C:
{noformat}

[documentation|https://docs.docker.com/reference/dockerfile/#notes-about-specifying-volumes]

See https://github.com/moby/moby/issues/41681

The Jenkins docker-image plugin should be updated to either:
1) fail/warn in this case
2) provide a way to configure the mount
3) mount non-C paths to C inside the container. Any variables that reference the non-C drive may need to be updated to use the C drive

Mark R made changes - 2024-11-22 22:28

Description

Original: If the workspace is on a different drive (in this case N) then docker.image fails with something like this:

{noformat}
00:00:07.112 $ docker run -d -t -w N:/myworkspace/myjob -v N:/myworkspace/myjob/:N:/myworkspace/myjob/ -v N:/myworkspace/myjob@tmp/:N:/myworkspace/myjob@tmp/ -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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** myregistry.com/myrepository/myimage:latest cmd.exe
. . .
00:00:08.850 java.io.IOException: Failed to run image 'myregistry.com/myrepository/myimage:latest'. Error: docker: Error response from daemon: hcs::CreateComputeSystem aa1593a84f9df2613191e56fa1b8037bd6d27a4b2c932a1b33e8b6e7f74961d0: The parameter is incorrect.
{noformat}

This is due to a limitation in docker on Windows:

{noformat}
Volumes on Windows-based containers: When using Windows-based containers, the destination of a volume inside the container must be one of:

a non-existing or empty directory
a drive other than C:
{noformat}

[documentation|https://docs.docker.com/reference/dockerfile/#notes-about-specifying-volumes]

See https://github.com/moby/moby/issues/41681

The Jenkins docker-image plugin should be updated to either:
1) fail/warn in this case
2) provide a way to configure the mount
3) mount non-C paths to C inside the container. Any variables that reference the non-C drive may need to be updated to use the C drive

New: If the workspace is on a different drive (in this case N) then docker.image fails with something like this:

{noformat}
00:00:07.112 $ docker run -d -t -w N:/myworkspace/myjob -v N:/myworkspace/myjob/:N:/myworkspace/myjob/ -v N:/myworkspace/myjob@tmp/:N:/myworkspace/myjob@tmp/ -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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** myregistry.com/myrepository/myimage:latest cmd.exe
. . .
00:00:08.850 java.io.IOException: Failed to run image 'myregistry.com/myrepository/myimage:latest'. Error: docker: Error response from daemon: hcs::CreateComputeSystem aa1593a84f9df2613191e56fa1b8037bd6d27a4b2c932a1b33e8b6e7f74961d0: The parameter is incorrect.
{noformat}

This is due to a limitation in docker on Windows:

{noformat}
Volumes on Windows-based containers: When using Windows-based containers, the destination of a volume inside the container must be one of:

a non-existing or empty directory
a drive other than C:
{noformat}

[documentation|https://docs.docker.com/reference/dockerfile/#notes-about-specifying-volumes] and [documentation|https://docs.docker.com/reference/cli/docker/container/run/#mount-volume--v---read-only]

See https://github.com/moby/moby/issues/41681

The Jenkins docker-image plugin should be updated to either:
1) fail/warn in this case
2) provide a way to configure the mount
3) mount non-C paths to C inside the container. Any variables that reference the non-C drive may need to be updated to use the C drive

Mark R made changes - 2024-11-22 22:36

Component/s

New: docker-workflow-plugin [ 20625 ]

Mark R made changes - 2024-11-22 22:37

Description

Original: If the workspace is on a different drive (in this case N) then docker.image fails with something like this:

{noformat}
00:00:07.112 $ docker run -d -t -w N:/myworkspace/myjob -v N:/myworkspace/myjob/:N:/myworkspace/myjob/ -v N:/myworkspace/myjob@tmp/:N:/myworkspace/myjob@tmp/ -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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** myregistry.com/myrepository/myimage:latest cmd.exe
. . .
00:00:08.850 java.io.IOException: Failed to run image 'myregistry.com/myrepository/myimage:latest'. Error: docker: Error response from daemon: hcs::CreateComputeSystem aa1593a84f9df2613191e56fa1b8037bd6d27a4b2c932a1b33e8b6e7f74961d0: The parameter is incorrect.
{noformat}

This is due to a limitation in docker on Windows:

{noformat}
Volumes on Windows-based containers: When using Windows-based containers, the destination of a volume inside the container must be one of:

a non-existing or empty directory
a drive other than C:
{noformat}

[documentation|https://docs.docker.com/reference/dockerfile/#notes-about-specifying-volumes] and [documentation|https://docs.docker.com/reference/cli/docker/container/run/#mount-volume--v---read-only]

See https://github.com/moby/moby/issues/41681

The Jenkins docker-image plugin should be updated to either:
1) fail/warn in this case
2) provide a way to configure the mount
3) mount non-C paths to C inside the container. Any variables that reference the non-C drive may need to be updated to use the C drive

New: If the workspace is on a different drive (in this case N) then docker.image fails with something like this:

{code:java}
docker.image('myregistry.com/myrepository/myimage:latest').inside {
sh 'echo test'
}
{code}

{noformat}
00:00:07.112 $ docker run -d -t -w N:/myworkspace/myjob -v N:/myworkspace/myjob/:N:/myworkspace/myjob/ -v N:/myworkspace/myjob@tmp/:N:/myworkspace/myjob@tmp/ -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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** myregistry.com/myrepository/myimage:latest cmd.exe
. . .
00:00:08.850 java.io.IOException: Failed to run image 'myregistry.com/myrepository/myimage:latest'. Error: docker: Error response from daemon: hcs::CreateComputeSystem aa1593a84f9df2613191e56fa1b8037bd6d27a4b2c932a1b33e8b6e7f74961d0: The parameter is incorrect.
{noformat}

This is due to a limitation in docker on Windows:

{noformat}
Volumes on Windows-based containers: When using Windows-based containers, the destination of a volume inside the container must be one of:

a non-existing or empty directory
a drive other than C:
{noformat}

[documentation|https://docs.docker.com/reference/dockerfile/#notes-about-specifying-volumes] and [documentation|https://docs.docker.com/reference/cli/docker/container/run/#mount-volume--v---read-only]

See https://github.com/moby/moby/issues/41681

The Jenkins docker-image plugin should be updated to either:
1) fail/warn in this case
2) provide a way to configure the mount
3) mount non-C paths to C inside the container. Any variables that reference the non-C drive may need to be updated to use the C drive

Mark R made changes - 2025-01-03 19:29

Attachment

New: WithContainerStepTest.java [ 63760 ]

Mark R made changes - 2025-01-03 19:29

Attachment

Original: WithContainerStepTest.java [ 63760 ]

Mark R made changes - 2025-01-08 04:07

Link

New: This issue relates to JENKINS-75087 [ JENKINS-75087 ]

Mark R made changes - 2025-01-08 04:11

Remote Link

New: This issue links to "Stack Overflow #63055516 (Web Link)" [ 30485 ]

Mark R made changes - 2025-01-08 20:17

Link

New: This issue relates to ~~JENKINS-75102~~ [ ~~JENKINS-75102~~ ]

Mark R made changes - 2025-01-17 19:39

Remote Link

New: This issue links to "Github #41681 (Web Link)" [ 30498 ]

Assignee:: Nicolas De Loof

Reporter:: Mark R

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2024-11-22 22:25

Updated:: 2025-01-17 19:39

Jenkins

Details

Description

Attachments

Issue Links

Activity

People

Dates