https://bugzilla.redhat.com/show_bug.cgi?id=1185423
Bug ID: 1185423
Summary: MountFlags=private in docker.service prevents admin
from exposing new storage to docker
Product: Fedora
Version: 21
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: lars(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
jchaloup(a)redhat.com, jperrin(a)centos.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
Setting MountFlags=private in docker.service means that any storage mounted on
the host after starting Docker will be unavailable for docker containers. For
example, I wanted to expose a directory from a remote server to a Docker
container:
mkdir /data/content
mount remote-server:/vol/content /data/content
docker run -v /data/content:/content larsks/thttpd -d /content
This fails because Docker does not see the mount onto /data/content. It only
sees the content of the underlying directory, not the mounted filesystem.
I think we want MountFlags=slave instead, which would prevent mounts inside the
Docker mount namespace from propagating to the global namespace while still
allowing global mounts to be available to docker containers.
--
You are receiving this mail because:
You are on the CC list for the bug.