You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "haosdent (JIRA)" <ji...@apache.org> on 2015/10/01 19:58:26 UTC

[jira] [Commented] (MESOS-3549) Log docker commands

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

haosdent commented on MESOS-3549:
---------------------------------

[~bobrik] I think we could change docker run command level because run command is important, other command keep current level would be better. But need [~tnachen] confirm whether this is accepted.

> Log docker commands
> -------------------
>
>                 Key: MESOS-3549
>                 URL: https://issues.apache.org/jira/browse/MESOS-3549
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker, slave
>            Reporter: Ian Babrou
>
> Command executor logs command it is about to run to stdout, this is really handy if things break:
> {noformat}
> Registered executor on 36com33.in.cfops.it
> Starting task sleepy.7c95443e-6697-11e5-9c9e-2c600c83f269
> sh -c 'echo $PORT && sleep 3600'
> Forked command at 1887
> 8921
> {noformat}
> Docker executor doesn't do anything like this. In fact, I often find myself looking at ps, strace or any other similar tool output to see what command was actually used to run the container. Seeing this in sandbox can save me and possibly other people time figuring out what is wrong with their tasks.



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