[jira] [Commented] (MESOS-1740) Bad error message when docker containerizer isn't enabled

["Timothy Chen (JIRA)" <ji...@apache.org>]

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

Timothy Chen commented on MESOS-1740:
-------------------------------------

I'll update it to use the first suggested message. I'd prefer not to check for each derived class type from the base pointer in the slave.

> Bad error message when docker containerizer isn't enabled
> ---------------------------------------------------------
>
>                 Key: MESOS-1740
>                 URL: https://issues.apache.org/jira/browse/MESOS-1740
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>            Reporter: Jay Buffington
>            Assignee: Timothy Chen
>            Priority: Minor
>
> If I set container in TaskInfo's executor (aka DockerInfo) but I do not start the slave with {{--containerizer=docker,...}} then I get this error message in the log:
> {noformat}
> E0827 17:53:16.422735 20090 slave.cpp:2491] Container 'xxx' for executor 'yyy' of framework 'zzz' failed to start: TaskInfo/ExecutorInfo not supported
> {noformat}
> A better error message would have been:
> {noformat}
> No enabled containerizers could create a container for the provided TaskInfo/ExecutorInfo message.  Enabled containerizers are: mesos.
> {noformat}
> An even better error message would have been:
> {noformat}
> DockerInfo was sent, but docker containerizer is not enabled.  Try adding --containerizer=docker,... to command line args
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)