Docker Desktop: Mounts denied: The path is not shared from the host and is not known to Docker
Docker Desktop (macOS) can only bind-mount folders listed under Settings → Resources → File sharing.
Seen on:
Docker
Meaning
Docker Desktop runs Linux in a VM; only shared host folders are visible to it. /Users is shared by default, but /Volumes, /opt, /private/var or external drives are not.
Common causes
- Path outside the shared folders (/Volumes, /opt, /tmp symlinks)
- Shared folder list edited/reset
- Using a symlinked path
⚡ Quick fix
- Add the folder in Docker Desktop → Settings → Resources → File sharing
- Move the project under your home directory
- Use the real path, not a symlink
Detailed fix by platform
Docker Desktop
# Settings → Resources → File sharing → + /Volumes/Work → Apply & restart
How to diagnose
- Path — Real path (pwd -P)
- Shares — Docker Desktop file sharing list
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- bind source path does not exist invalid mount config for type "bind": bind source path does not exist
- FailedMount Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition
- Multi-Attach error Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another
Most viewed in Docker
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026