[jira] [Commented] (MESOS-8257) Unified Containerizer "leaks" a target container mount path to the host FS when the target resolves to an absolute path

["Chun-Hung Hsiao (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581694#comment-16581694 ] 

Chun-Hung Hsiao commented on MESOS-8257:
----------------------------------------

[~jasonlai] Do you plan to land this in this week? Should this ticket block the 1.7.0 release?

> Unified Containerizer "leaks" a target container mount path to the host FS when the target resolves to an absolute path
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-8257
>                 URL: https://issues.apache.org/jira/browse/MESOS-8257
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>    Affects Versions: 1.3.1, 1.4.1, 1.5.0
>            Reporter: Jason Lai
>            Assignee: Jason Lai
>            Priority: Critical
>              Labels: bug, containerizer, mountpath
>
> If a target path under the root FS provisioned from an image resolves to an absolute path, it will not appear in the container root FS after {{pivot_root(2)}} is called.
> A typical example is that when the target path is under {{/var/run}} (e.g. {{/var/run/some-dir}}), which is usually a symlink to an absolute path of {{/run}} in Debian images, the target path will get resolved as and created at {{/run/some-dir}} in the host root FS, after the container root FS gets provisioned. The target path will get unmounted after {{pivot_root(2)}} as it is part of the old root (host FS).
> A workaround is to use {{/run}} instead of {{/var/run}}, but absolute symlinks need to be resolved within the scope of the container root FS path.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)