[
https://issues.apache.org/jira/browse/MESOS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935004#comment-14935004
]
Ian Babrou commented on MESOS-3549:
-----------------------------------
I want to see some consistency here:
* If command executor prints the command, docker executor should do the same.
* If command executor doesn't do that, let docker executor do the same.
GLOG_v=1 made a lot of noise I didn't want the last time I checked.
> 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)
