# "bind source path does not exist" when creating bind mount from within a container

**URL:** <https://forums.docker.com/t/bind-source-path-does-not-exist-when-creating-bind-mount-from-within-a-container/97785>\
**Category:** Docker Desktop\
**Tags:** windows\
**Created:** [August 18, 2020, 11:53pm UTC](https://forums.docker.com/t/bind-source-path-does-not-exist-when-creating-bind-mount-from-within-a-container/97785 "2020-08-18T23:53:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tthacker](https://avatars.discourse-cdn.com/v4/letter/t/ea5d25/32.png) [@tthacker](https://forums.docker.com/u/tthacker)\
**Post date:** [August 18, 2020, 11:53pm UTC](https://forums.docker.com/t/bind-source-path-does-not-exist-when-creating-bind-mount-from-within-a-container/97785/1 "2020-08-18T23:53:36Z")

</div>

Using docker for windows with WSL2 I have mounted the docker socket to a container running the docker image:

docker run -ti -v /var/run/docker.sock:/var/run/docker.sock docker

In this container I try to run another container (doesn’t matter which container) and bind mount a file from the windows host machine to the 2nd new container:

docker run --mount type=bind,src=/C/Users/…/test.yml,dst=/test.yml docker

I get the following error:

docker: Error response from daemon: invalid mount config for type “bind”: bind source path does not exist: /C/Users/…/test.yml.

Yes the path does exist, running the 2nd command directly from the host windows machine works  
I am using WSL2, with Hyper-V it worked but only after doing a docker login from inside the container.

- Windows Version: 10.0.19041
- Docker Desktop Version: 2.3.0.4

This issue is similar but the solution they talk about doesn’t work on WSL2: [https://github.com/docker/for-win/issues/6628](https://github.com/docker/for-win/issues/6628)

Does anyone else have this issue or know why it could be happening?  
Has anyone encounter