[
https://issues.apache.org/jira/browse/MESOS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063651#comment-14063651
]
Jay Buffington commented on MESOS-1527:
---------------------------------------
[~tarnfeld] Yes, IMO, if the protobuf message specifies multiple containerizers
the dispatcher (ComposingContainerizer) should try the first containerizer
specified in the --containerizers which matches the protobuf and if that fails,
try the next one. In pseudo code, that'd look like this:
{noformat}
for each containerizer, in the order specified in --containerizers
if protobuf specifies this containerizer
if launch containerizer succeeds
return success
{noformat}
> Choose containerizer at runtime
> -------------------------------
>
> Key: MESOS-1527
> URL: https://issues.apache.org/jira/browse/MESOS-1527
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Reporter: Jay Buffington
>
> Currently you have to choose the containerizer at mesos-slave start time via
> the --isolation option. I'd like to be able to specify the containerizer in
> the request to launch the job. This could be specified by a new "Provider"
> field in the ContainerInfo proto buf.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
