You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Yan Xu (JIRA)" <ji...@apache.org> on 2015/09/05 00:09:45 UTC
[jira] [Created] (MESOS-3373) Drop the restrictions that disallow
nonexistent absolute volume container path if a rootfs is used.
Yan Xu created MESOS-3373:
-----------------------------
Summary: Drop the restrictions that disallow nonexistent absolute volume container path if a rootfs is used.
Key: MESOS-3373
URL: https://issues.apache.org/jira/browse/MESOS-3373
Project: Mesos
Issue Type: Bug
Reporter: Yan Xu
Such a restriction is enforced because:
{noformat:title=}
// An absolute path must already exist. This is because we want
// to avoid creating mount points outside the work directory in
// the host filesystem or in the container filesystem root.
{noformat}
See [the relevant code|https://github.com/apache/mesos/blob/7f2bcc7d7171582bb731f030504a063bc5c7c5a1/src/slave/containerizer/isolators/filesystem/linux.cpp#L392].
However when a new rootfs is used, we don't need to worry about this.
This of course requires the rootfs to be writable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)