docker-compose up converts linux path to windows for volumes

[AlekseiPavlov-GC]

Hi colleagues,

Steps to reproduce

Docker 3.1.0 (51484) running with WSL2 on Windows 10 version 1909.

I try to execute the script using Windows Powershell 7.1:
docker-compose -f "docker-compose.generated.json" up --build --remove-orphans --renew-anon-volumes --force-recreate --always-recreate-deps

The json file has the following section:

"volumes": {
       "inputansibleconfigvolume": {
          "driver_opts": {
             "type": "none",
             "device": "${ANSIBLE_CONFIGS}",
             "o": "bind"
          }
       }
    }

The Environment Variable ANSIBLE_CONFIGS is set to: /c/Dev/Git/folder

When I execute the command:
docker-compose -f "docker-compose.generated.json" up --build --remove-orphans --renew-anon-volumes --force-recreate --always-recreate-deps

A docker volume is created.

Actual:
device: "C:\c\Dev\Git\folder"
Or depending on different manipulations device value can be a slightly different but always in Windows style.

Expected:
device: "/c/Dev/Git/folder"

I tried:
COMPOSE_CONVERT_WINDOWS_PATHS=1
COMPOSE_CONVERT_WINDOWS_PATHS=0

This had no effect.

Workaround:

"volumes": {
       "inputansibleconfigvolume": {
          "external" true
       }
    }

docker volume create --name inputansibleconfigvolume -o type=none -o device=/c/Dev/Git/folder -o o=bind

Could you please check this?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[LaXiS96]

Hi, I am pretty sure the cause for this issue is the same as this one: #7856 (comment)

TLDR, in commit 8c81a9d relative path handling was added to driver_opts.device. I don't know how this change was tested, but the simple use case of running docker-compose on Windows to deploy on a Linux remote machine with a bind mounted volume, breaks.
The problem is that the path is run through os.path.abspath on the local machine, which in this case converts a Linux path to Windows separators and adds C:.
I'm still waiting for any input from @aiordache. The quickest solution would be to revert to not handling relative paths, or better handle them on the Docker daemon host instead of the docker-compose client.

Also related: #7893

--- EDIT
Ok so I found the original PR: #7762
And I can see that it's really not the first instance that this problem was reported.
See comments in PR and also: #7900

[stale]

This issue has been automatically marked as not stale anymore due to the recent activity.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it had not recent activity during the stale period.