[
https://issues.apache.org/jira/browse/MESOS-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112685#comment-14112685
]
Timothy Chen commented on MESOS-1725:
-------------------------------------
So the intention earlier was that we stream logs from the running container
into the sandbox task logs. If we cannot launch a container we log the stderr
message into the slave logs. You should see your command failure message in the
slave logs as part of the "failed to launch container: ........."
> Docker logs aren't appended to sandbox/stderr when container fails to start
> ---------------------------------------------------------------------------
>
> Key: MESOS-1725
> URL: https://issues.apache.org/jira/browse/MESOS-1725
> Project: Mesos
> Issue Type: Bug
> Reporter: Jay Buffington
> Assignee: Timothy Chen
> Labels: docker
>
> If the docker containerizer fails to launch a docker container (say, because
> of a bogus command) the logs will not be written to the sandbox's stderr.
> This is because the logic of DockerContainerizerProcess doesn't account for
> calling "docker logs" when it encounters an error.
> As an aside, I think there might also be a separate bug that is related where
> a docker container which runs successfully and exits quickly will result in
> the docker containerizer incorrectly reporting failure.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
