[
https://issues.apache.org/jira/browse/MESOS-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104296#comment-14104296
]
Jay Buffington commented on MESOS-1725:
---------------------------------------
[~tnachen] I think I tracked down the other case. It's a race between "docker
inspect" and "docker run". I filed MESOS-1726 for that. That jira and this
one are related.
> 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)
