# Error response from daemon: error while mounting volume '/host_mnt/c/Users/user/data': permission denied

- **ID:** `docker/volume-mount-permission-denied-windows`
- **Domain:** docker
- **Category:** system_error
- **Verification:** ai_generated
- **Fix Rate:** 78%

## Root Cause

On Docker Desktop for Windows, bind mounts from the C drive require shared drive permissions; if the drive is not shared or the user lacks access, mounting fails with permission denied.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Docker Desktop 4.19.0 | active | — | — |
| Docker Desktop 4.22.1 | active | — | — |
| Windows 10 21H2 | active | — | — |
| Windows 11 22H2 | active | — | — |

## Workarounds

1. **Share the C drive in Docker Desktop: Settings > Resources > File Sharing > add 'C:\' and apply. Then restart Docker Desktop and retry the mount.** (85% success)
   ```
   Share the C drive in Docker Desktop: Settings > Resources > File Sharing > add 'C:\' and apply. Then restart Docker Desktop and retry the mount.
   ```
2. **Move your project folder to a drive that is already shared (e.g., D:\) or to the user profile directory under C:\Users\ which is often shared by default.** (75% success)
   ```
   Move your project folder to a drive that is already shared (e.g., D:\) or to the user profile directory under C:\Users\ which is often shared by default.
   ```
3. **Use a named volume instead of a bind mount: 'docker volume create mydata' and then 'docker run -v mydata:/app/data' to avoid host filesystem permission issues.** (70% success)
   ```
   Use a named volume instead of a bind mount: 'docker volume create mydata' and then 'docker run -v mydata:/app/data' to avoid host filesystem permission issues.
   ```

## Dead Ends

- **Running Docker Desktop as Administrator** — Even as Administrator, the C drive must be explicitly shared in Docker Desktop settings; admin privileges alone do not bypass the sharing requirement. (70% fail)
- **Changing file permissions on the host folder using icacls** — Docker Desktop uses a virtual filesystem (gRPC FUSE) to mount Windows paths; host NTFS permissions are not the primary issue—the Docker service itself needs share access. (80% fail)
- **Using a relative path instead of absolute path in docker run -v** — Relative paths are resolved relative to the current directory, but if the resolved absolute path is still on a non-shared drive, the same error occurs. (60% fail)