Created
May 12, 2014 20:03
-
-
Save apatil/930cd0e0bf037086a51f to your computer and use it in GitHub Desktop.
CoreOS/Docker mount propagation tests
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Test 1: | |
# Launch data-only container in privileged mode | |
sudo docker run -i -t --name dataonly --privileged -v /shared ubuntu:14.04 /bin/bash | |
# in container: | |
mdir /shared/usr | |
mount --bind /usr /shared/usr | |
# Launch client container and attempt to read data from data-only container | |
sudo docker run -i -t --volumes-from dataonly ubuntu:14.04 /bin/bash | |
ls /shared/usr | |
# empty |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As far as I can tell there is no way to directly expose a fuse filesystem mounted inside a container back to the host or other containers. I've been researching this issue for a couple days and the only "solution" would be to mount the fuse filesystem and expose it using a NFS share or similar.