You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Timothy Chen (JIRA)" <ji...@apache.org> on 2014/08/20 06:53:18 UTC
[jira] [Updated] (MESOS-1725) Docker logs aren't appended to
sandbox/stderr when container fails to start
[ https://issues.apache.org/jira/browse/MESOS-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Chen updated MESOS-1725:
--------------------------------
Labels: docker (was: )
> 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
> 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)