New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot bind mount a file that already exists in the container #5
Comments
Having this issue myself:
Docker:
Docker Compose:
Windows: |
Same problem here when using compose. It fails to mount those files
Tried both with stable and beta24. |
+1 me too |
Hm, this works for me:
Is this a compose-specific problem? |
@oparoz @maltyxx @matevarga Could you please test with Beta25 that was released two days ago. It contains some fixes related to file mounting. If you still have the issue, could you confirm:
|
Here is an example which still doesn't work:
|
And regarding the test
Not sure if that's relevant, but I created the file manually and then
|
Same problem on beta26 |
Same problem here
this also did not work for me
|
Apparently fixed on beta27 |
Hi everyone, is it fixed for all of you with Beta27? I'm going to tag the ticket as "will be closed" and will close it in a week of so if nobody complains :-) Thanks again for your reports! |
Hi, I'm closing the issue has said a week ago. Feel free to reopen if the issue is still there, of course! |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
C:\Users\m\src\phr\docker\local [develop ≡]> docker run -it -v C:\Users\m\src\phr\docker\local\broker-config.yml:/cryptoservice/broker-config.yml image-name bash
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: oci runtime error: rootfs_linux.go:53: mounting "/var/lib/docker/aufs/mn t/90d24356afdeb7b9ddad4b3b6903be92063151c33bf34f3d63ede464437060c6/cryptoservice/broker-config.yml" to rootfs "/var/lib/docker/aufs/mnt/90d24356afdeb7b9ddad4 b3b6903be92063151c33bf34f3d63ede464437060c6" caused "not a directory".
Expected behavior
Similarly to how Docker behaves on Linux, the container should start.
Actual behavior
See above
Information
This happens on Win10 latest (1511?) + Docker 1.12, and with Mac as well (can't provide version for now).
I'll try to make an image with which this is reproducible.
The text was updated successfully, but these errors were encountered: