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
Missing secrets file creates a directory? #5377
Comments
It's a somewhat unfortunate side-effect of the way we emulate secrets in |
#5363 was never merged, which means this may never have been fixed. Consider re-opening? |
It was fixed by #5415 |
Hi @shin- I just encountered this issue with docker-compose in WSL.
Output of docker-compose version 1.29.0, build 07737305
docker-py version: 5.0.0
CPython version: 3.7.10
OpenSSL version: OpenSSL 1.1.0l 10 Sep 2019 If you need more input please just let me know. Maybe this is just how bind mounts work. It took me a while to figure out that I had to delete the created folder in /wsl/docker-desktop-bind-mounts too before I could add my missing secret file to make it work again. Update: |
I'm also seeing this behavior (a missing secrets file results in a directory created when the composition is started) with Docker Desktop for Windows (v3.3.1 b63152, with WSL2 engine enabled) but, interestingly, not with Docker Desktop for Mac (v3.3.1 b63152). |
When docker-compose up with the config below, if the file mypass.txt is missing, docker-compose creates an empty directory mypass.txt. Is that expected behaviour?
macOS 10.13.1
Docker version 17.11.0-ce-rc3, build 5b4af4f
docker-compose version 1.17.0, build ac53b73
The text was updated successfully, but these errors were encountered: