Container should start normally
C:\Users\einom>docker start f96263b10996 Error response from daemon: error while creating mount source path '/host_mnt/c/Users/einom/Documents/projects/cap/src': mkdir /host_mnt/c: file exists Error: failed to start containers: f96263b10996
Docker version: 17.12.0-ce-win47 (15139)
Windows 10 Pro Version: 1709 Build: 16299.192
Whole C drive is shared with docker VM
Of cource it exists because if I understand correctly this /host_mnt/c should point to my whole C: drive ?
I had the same issue. I was able to resolve it by running: docker volume rm -f [name of docker volume with error] Then restarting docker, and running: docker-compose up -d --build
I tried these same steps without restarting my docker, but restarting my computer and that didn't resolve the issue. What resolved the issue for me was removing the volume with the error, restarting my docker, then doing a build again.
Unsure if you did, but please can you kindly explain the meaning of the "-d" and "--build" in "docker-compose up -d --build" please?
I don't mean "this is what the man-page says", rather I mean what is the human explanation of the flags?
Also, this worked perfectly for me, I had to restart the host machine aswell.