Docker Desktop: Document Mingw/msys2 POSIX path conversion in troubleshooting section

[thaJeztah]

Problem description

Users on Windows that use Mingw/msys2 for their shell may be running in the problem that that shell does "POSIX path conversion", see docker/for-win#6754 (comment)

Relates to docker/for-win#6875, docker/for-win#6754

Given that this "feature" can be confusing and lead to "surprising" issues, I think we should have a mention of this behaviour (and workarounds) in our documentation (probably under the "troubleshooting" section for Docker Desktop for Windows).

Problem location

• I saw a problem on the following URL:

• I couldn't find the information I wanted. I expected to find it near the following URL:

• Other:

Project version(s) affected

Suggestions for a fix

[thaJeztah]

@stephen-turner @usha-mandya @StefanScherer (I kept forgetting to open an issue for this)

[thaJeztah]

FWIW; I could use some help on this with the right terminology / description. I'm not really sure in what cases/situations people are using mingw/msys2.

[StefanScherer]

Hello, Mac user here 👋,
but happy to try to understand Windows use-cases.

What I learned is that Git for Windows brings a Git Bash which seems to be one popular way to do Git and some Linuxish commands on Windows in a pre-WSL world. I don't know if that matches msys2, as there is a standalone https://www.msys2.org/ installer as well. 🤔
I went through these some years ago before I switched over to a MacBook Pro.

WSL 1 and now WSL 2 is coming to more and more users and I hope that will "fix" the situation on Windows, but my guess is that we will live for some years with all the spectrum of shells and tools.

[thaJeztah]

Yes, perhaps people should use alternatives. I mostly opened this because when you hit this issue, it's really "unexpected" (why is it using these weird paths? I didn't specify them!), so if we somehow could point people to the options/workarounds, I think that's a good thing

[docker-robott]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked