-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[BUG] Starting with version 2.29.3 Binding Mounts do not work anymore with windows containers. #12137
Comments
regression on 2.29.5 is caused by cb00aaa - I would have expected windows container engine to just ignore the error you reported on 2.29.3 is harder to diagnose. I checked |
Tested my PR with a short-syntax bind mount on windows with windows-containers-enabled-engine and can't reproduce the reported issue. Would you have a chance to give it a try ? |
Also reported in; That one also reported the
|
fixed by #12141 |
Description
Version 2.29.3:
Using volumes in services defined in docker compose with short syntax (VOLUME:CONTAINER_PATH) give this error when doing "docker compose up": Error response from daemon: hcs::CreateComputeSystem : The request is not supported.
Version 2.29.5:
Using volumes in services defined in docker compose with short syntax (VOLUME:CONTAINER_PATH) give this error when doing "docker compose up": Error response from daemon: invalid mount config for type "bind": invalid propagation mode: rprivate.
This worked all fine, up until version 2.29.2, inclusively.
From Docker docs "Bind propagation defaults to rprivate for both bind mounts and volumes. It is only configurable for bind mounts, and only on Linux host machines."
We need to have this working again on Windows Host machines as well.
Please provide a fix or a workaround.
Steps To Reproduce
Environment: Windows Host Machines
Add any service in a docker compose file and define volumes with short syntax:
e.g.
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: