[
https://issues.apache.org/jira/browse/MESOS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063323#comment-14063323
]
Tom Arnfeld commented on MESOS-1527:
------------------------------------
Sorry for the potentially dumb question, a little out of the loop. Could this
also be applicable for when a containerizer actually *fails* to launch a
container due to some unexpected error, for example if the Docker daemon is not
running.
Correct me if i'm wrong, but this patch is being used to determine the
waterfall effect when specifying multiple containerizers? Perhaps it could be
extended to also fix MESOS-1462, or would you consider that another concern?
> 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)
