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

Stavros Kontopoulos commented on MESOS-1740:
--------------------------------------------

I am using mesos 0.25.0 with marathon and i never got that message instead i 
got several of the following messages in the ERROR/WARNING log (try to grep it 
but no result):

E1117 12:28:48.029485 17758 slave.cpp:660] Failed to attach file 
'/tmp/mesos/slaves/b36f29ca-47c1-49cc-aaa8-9482c42e966c-S0/frameworks/b36f29ca-47c1-49cc-aaa8-9482c42e966c-0000/executors/ubuntu2.284840e3-8d1d-11e5-bc79-024246e9a1aa/runs/930c586f-b93e-44e4-ab73-1e4d93f9d6d3':
 Failed to get realpath of 
'/tmp/mesos/slaves/b36f29ca-47c1-49cc-aaa8-9482c42e966c-S0/frameworks/b36f29ca-47c1-49cc-aaa8-9482c42e966c-0000/executors/ubuntu2.284840e3-8d1d-11e5-bc79-024246e9a1aa/runs/930c586f-b93e-44e4-ab73-1e4d93f9d6d3':
 No such file or directory

Should not this message be emitted in any step of launching a docker image when 
docker containerizer is not enabled?

Then i switched docker containerizer on (by accident dint have it on) and 
everything runs fine... 

> 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
>              Labels: docker
>             Fix For: 0.20.1
>
>
> 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)

Reply via email to