Docker
Docker run failed in Git Bash because the mount destination was not absolute
docker: Error response from daemon: OCI runtime create failed: invalid mount {Destination:\Program Files\Git\work Type:bind Source:/run/desktop/mnt/host/c/Users/user/work;C Options:[rbind rprivate]}: mount destination \Program Files\Git\work not absolute: unknown.Docker Desktop received a malformed mount destination because Git Bash rewrote the path expression before Docker evaluated the bind mount.
Observed message
docker: Error response from daemon: OCI runtime create failed: invalid mount {Destination:\Program Files\Git\work Type:bind Source:/run/desktop/mnt/host/c/Users/user/work;C Options:[rbind rprivate]}: mount destination \Program Files\Git\work not absolute: unknown.Why it happens
- Git Bash preprocessed $(pwd) or the provided path and produced an invalid mount destination.
- The bind mount used path formatting that Docker Desktop could not parse correctly on Windows.
How to fix it
- Disable Git Bash path conversion temporarily when invoking docker run.
- Use the Docker-documented path formatting for Git Bash on Windows.
- Switch to PowerShell or cmd.exe if path rewriting continues to interfere with the mount.
