Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Allow controlling the mount namespace #10088
This is a continuation of a request & discussion in #6687
Currently if you mount something on top of a docker volume inside a container, and you share that volume with another container, the mount appears empty.
Since the processes inside the container need to see their root as the root of the image, we can instead use a simple
This is also needed to access network namespaces that are created within a container due to the proc mount (typically at /run/netns/<net_namespace>).
EDIT: This is no longer a valid concern for >1.6 docker since the mount namespace is notlonger private and mount propogation works