docs: note Git Bash path conversion silently breaks the /zap/wrk mount

[SalmanDEmad]

When running the packaged scans (e.g. zap-full-scan.py) with docker run -v <host>:/zap/wrk/:rw ... from Git Bash / MSYS on Windows, the mount silently fails and the scan reports:

A file based option has been specified but the directory '/zap/wrk' is not mounted

The cause is not ZAP-specific: Git Bash automatically converts POSIX-style paths in command arguments to Windows paths, which mangles the container side of the -v host:container argument to docker run. This is a well-known MSYS behavior that affects any docker run -v invocation.

This PR adds a short > [!NOTE] callout to the "Mounting the Current Directory" section of the docker docs, next to the existing CWD mount examples, listing the three standard workarounds:

• prefix the container path with an extra slash (//zap/wrk/),
• set MSYS_NO_PATHCONVERSION=1 for the command, or
• run the docker run command from PowerShell or CMD instead.

Docs-only change, single file (site/content/docs/docker/about.md).

[psiinon]

Checkmarx One – Scan Summary & Details – efffed7c-0af6-4ec2-9b15-64fd96e046bf

Great job! No new security vulnerabilities introduced in this pull request

---

Communicate with Checkmarx by submitting a PR comment with @Checkmarx followed by one of the supported commands. Learn about the supported commands here.

[thc202]

Finding working solutions for all environments is outside the scope of this document.

I'd prefer we didn't have to document all idiosyncrasies of all envs.

[psiinon]

How about documenting these sort of things on https://www.zaproxy.org/docs/docker/diagnosing-problems/
Of a new FAQ? https://www.zaproxy.org/faq/