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

Jie Yu commented on MESOS-9009:
-------------------------------

commit b866fc3278dc4fd48d1a50493bcde1efdfa91cc7 (HEAD -> master, origin/master, 
origin/HEAD)
Author: Jason Lai <[email protected]>
Date:   Sun Nov 18 21:12:28 2018 -0800

    Added unit tests for Stout `path::normalize` function in POSIX.

    Review: https://reviews.apache.org/r/68832/

commit 516c0bd70c50ae5aa6682b3b8675ef75d99dfc3f
Author: Jason Lai <[email protected]>
Date:   Sun Nov 18 21:12:06 2018 -0800

    Added Stout `path::normalize` function for POSIX paths.

    Added `path::normalize` to normalize a given pathname and remove
    redundant separators and up-level references.

    This function follows the rules described in `path_resolution(7)`
    for Linux. However, it only performs pure lexical processing without
    touching the actual filesystem.

    Review: https://reviews.apache.org/r/65811/

> Support for creation non-existing host paths in a whitelist as source paths
> ---------------------------------------------------------------------------
>
>                 Key: MESOS-9009
>                 URL: https://issues.apache.org/jira/browse/MESOS-9009
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization
>    Affects Versions: 1.8.0
>            Reporter: Jason Lai
>            Assignee: Jason Lai
>            Priority: Major
>              Labels: containerizer, mount, path
>
> Docker creates a directory specified in {{docker run}}'s {{--volume}}/{{-v}} 
> option as the source path that will get bind-mounted into the container, if 
> the source location didn't originally exist on the host.
> Unlike Docker, UCR bails on launching containers if any of their host mount 
> paths doesn't originally exist. While this is more secure and eliminates 
> unnecessary side effects, it breaks transparent compatibility when trying to 
> migrate from Docker.
> As a trade-off, we should allow host path creation in a restricted manner, by 
> introducing a new Mesos agent flag ({{--host_path_volume_force_creation}}) as 
> a colon-separated whitelist (similar to the format of POSIX's {{$PATH}} 
> environment variable), under whose items' subdirectories the host paths are 
> allowed to be created.



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

Reply via email to