[
https://issues.apache.org/jira/browse/MESOS-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jie Yu updated MESOS-7306:
--------------------------
Description:
Currently, all mounts in a container are marked as 'slave' by default. However,
for some cases, we may want mounts under certain directory in a container to be
propagate back to the root mount namespace. This is useful for the case where
we want the mounts to survive container failures.
See more documentation about mount propagation in:
https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt
Given mount propagation is very hard for users to understand, probably worth
limiting this to just host volumes because we only see use case for that at the
moment.
was:
Currently, all mounts in a container are marked as 'slave' by default. However,
for some cases, we may want mounts under certain directory in a container to be
propagate back to the root mount namespace. This is useful for the case where
we want the mounts to survive container failures.
See more documentation about mount propagation in:
https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt
> Support mount propagation for host volumes.
> -------------------------------------------
>
> Key: MESOS-7306
> URL: https://issues.apache.org/jira/browse/MESOS-7306
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Reporter: Jie Yu
> Assignee: Qian Zhang
> Labels: mesosphere, storage
>
> Currently, all mounts in a container are marked as 'slave' by default.
> However, for some cases, we may want mounts under certain directory in a
> container to be propagate back to the root mount namespace. This is useful
> for the case where we want the mounts to survive container failures.
> See more documentation about mount propagation in:
> https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt
> Given mount propagation is very hard for users to understand, probably worth
> limiting this to just host volumes because we only see use case for that at
> the moment.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
