This repository has been archived by the owner. It is now read-only.
1786.0.1 - Docker 18.05.0-ce has a bind mount bug that prevents containers with volumes from starting #2440
Comments
I can repro this (thanks for the easy repro). Tested the fixed and confirmed it worked. Working on backporting this now. |
Closed via coreos/coreos-overlay#3248 which should be in Alpha 1786.1.0, which should be released soon |
Thank you, all! That was hella quick. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Report
Bug
Docker 18.05.0-ce has a bind mount bug that prevents containers from starting.
Issue: moby/moby#37032
Fix: moby/moby#37031
Container Linux Version
Environment
What hardware/cloud provider/hypervisor is being used to run Container Linux?
AWS
Expected Behavior
kubernetes / kubelet managed containers w/ bind mounted volumes start
Actual Behavior
"Error": "linux mounts: Could not find source mount of /etc/coreos"
Reproduction Steps
docker run -it --rm --mount type=bind,source=/etc/coreos,target=/etc/coreos,bind-propagation=rslave busybox /bin/sh
Other Information
partial output of
docker inspect
for failing container-linux-update-agent containerThe text was updated successfully, but these errors were encountered: