[
https://issues.apache.org/jira/browse/MESOS-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829156#comment-15829156
]
Gilbert Song commented on MESOS-3373:
-------------------------------------
In linux.cpp, the error you see is for the case that the container shares the
host's rootfs (no image defined). For the container image cases (a new rootfs
provided), the absolute container path is allowed and will be created.
> 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)
