Docker Git Bash Guide

What it does

This skill provides guidance and solutions for handling Docker commands within a Git Bash (MINGW) environment on Windows. It specifically addresses issues arising from automatic path conversion that can break volume mounts and other Docker operations. The skill helps users understand when and why these conversions occur, and offers a recommended solution to prevent them.

When to use it

• When encountering errors with Docker volume mounts in Git Bash (MINGW).
• When running Docker commands from within a MINGW or MSYS2 shell on Windows.
• To troubleshoot unexpected behavior when using Docker paths that include forward slashes (/).
• When needing to ensure correct path formatting for Docker commands executed in Git Bash.

Key capabilities

• Path Conversion Explanation: Clearly explains how Git Bash (MINGW) automatically converts Unix-style paths when executing Windows executables like docker.exe.
• Trigger Identification: Identifies specific patterns that trigger automatic path conversion, such as leading forward slashes and colon-separated paths.
• Environment Detection: Provides methods to detect if you are running in a Git Bash/MINGW environment using environment variables (MSYSTEM, uname).
• Solution: MSYS_NO_PATHCONV: Offers the recommended solution of prefixing Docker commands with MSYS_NO_PATHCONV=1 to disable automatic path conversion.

Example prompts

• "How do I mount a volume in Docker when using Git Bash?"
• "Why are my Docker paths being converted incorrectly in MINGW?"
• "What is MSYS_NO_PATHCONV and how do I use it with Docker?"
• "How can I tell if I'm running Docker commands in a Git Bash environment?"

Tips & gotchas

• MSYS_NO_PATHCONV is Recommended: For Git Bash users, using MSYS_NO_PATHCONV=1 before your Docker command is the most reliable solution to prevent path conversion issues.
• Environment Detection: The $MSYSTEM environment variable provides the most reliable indication of running in a Git Bash/MINGW environment.
• Understand Triggers: Be aware of the specific patterns (leading /, colons) that trigger automatic path conversion within Git Bash.