[
https://issues.apache.org/jira/browse/MESOS-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285919#comment-14285919
]
Dominic Hamon commented on MESOS-2221:
--------------------------------------
It seems like that flexibility is going to be good practice anyway.
So how about, for this specific use-case:
{noformat}
message Offer {
...
optional Container container;
}
message Container {
repeated Type type;
}
{noformat}
Note the type here is repeated to cover the case of a composing containerizer.
> Include supported containerizers in resource offers
> ---------------------------------------------------
>
> Key: MESOS-2221
> URL: https://issues.apache.org/jira/browse/MESOS-2221
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Bill Farner
> Labels: twitter
>
> It would be nice if the slave could advertise to the scheduler which
> containerizers it supports. As it stands, the scheduler must count on
> external knowledge of whether a task is supported by a slave. For example, a
> scheduler cannot automatically notice that a slave does not have the docker
> containerizer enabled, and may fatefully try to launch docker tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
