Using bind mounts with nonexistent directory leads to error

[ethancn]

File: storage/bind-mounts.md

As the doc above said, when using bind mounts, "The file or directory does not need to exist on the Docker host already. It is created on demand if it does not yet exist", but this is not the same as what I tested.

I ran the following command with a nonexistent directory /home/workspace/app,

docker run -it \
  --name mycontainer \
  --mount type=bind,src="$(pwd)"/app,dst=/usr/src/app \
  alpine:latest

and got this error: invalid mount config for type "bind": bind source path does not exist: /home/workspace/app.

I think the doc is incorrect about this. The host is CentOS 7 with Docker 19.03.5 installed.

[thaJeztah]

This is the expected behavior, and described here; https://docs.docker.com/storage/bind-mounts/#differences-between--v-and---mount-behavior

Differences between -v and --mount behavior

If you use --mount to bind-mount a file or directory that does not yet exist on the Docker host, Docker does not automatically create it for you, but generates an error.

[ethancn]

This is the expected behavior, and described here; https://docs.docker.com/storage/bind-mounts/#differences-between--v-and---mount-behavior

Differences between -v and --mount behavior
If you use --mount to bind-mount a file or directory that does not yet exist on the Docker host, Docker does not automatically create it for you, but generates an error.

Thanks for reminding me, didn't notice the difference before. This issue can be closed.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked