[ https://issues.apache.org/jira/browse/MESOS-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776488#comment-16776488 ]
Gilbert Song commented on MESOS-9009: ------------------------------------- Done. Thanks for the patch! > 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 > Reporter: Jason Lai > Assignee: Jason Lai > Priority: Major > Labels: containerizer, mount, path > Fix For: 1.8.0 > > > 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)