Mention something in the considerations regarding bind mounts about Windows permissions.

[Skareeg]

Is this a docs issue?

• My issue is about the documentation content or website

Type of issue

I can't find what I'm looking for

Description

I spent a couple hours trying to fix an issue with bind mounts that many posts online indicate Windows Docker Desktop users are having, and not many of them mentioned a potential fix that worked completely. I request that either a suggestion / consideration is added, or that someone simply correct me in my understanding of how the permissions works regarding Docker Desktop not binding files into a folder.

Location

https://docs.docker.com/engine/storage/bind-mounts/

Suggestion

At the link anchor:
https://docs.docker.com/engine/storage/bind-mounts/#considerations-and-constraints

I would heavily recommend indicating that Windows and Docker Desktop sometimes does not copy files when doing bind mounts from folders that are not in the C:/Users/<username>/ directory or that Docker Desktop does not, by default, have access to. Alternatively, something could be mentioned about how to give the Docker daemon permissions to a folder on Windows or simply that it is just necessary to do so.

This likely warrants more testing or research, but I have noticed many posts online regarding Windows files not showing in bind mounts in the guest container, and moving things around did not solve anything up until I moved the folder into a user directory. This is clearly a permissions issue, so for newcomers, I would request that something be noted here regarding this. I had full access to the folder and files I was attempting to mount, but evidently the Docker daemon did not (or something along those lines), and this issue was resolved by moving the folder under my user directory (essentially Windows version of $HOME) after a couple hours of testing different mount settings and permissions settings.

[Skareeg]

I am aware that this is probably something a lot of folks already know how to address. This would simply be for newcomers or those that wouldn't initially think such a thing reading through docs. Personally, I had just assumed that Docker Desktop had the necessary permissions, but that may be incorrect, or something else is going on under the hood.