如何从App Creation命令获取Mesos Marathon Stdout？

如果我使用Marathon UI创build了一个新的应用程序，例如“badcommand”，那么没有与任务相关联的stdout / stderr（在Marathon UI或Mesos UI中）。 如何获得stdout / stderr？

我在下面列出了Marathon日志，但是它只是说任务（test2）失败了。 标准输出工作正常，与我的Docker容器。 我在文档中看到了一些信息，但没有提到这个问题。

对于我的实际使用情况，我试图运行一个bash脚本来创build一些数据库表。 显然，我可以创build一个扩展现有的Dockerfile，但是从Marathon运行脚本会更容易，因为如果我使用敏感信息创build自己的Dockerfile，而不是使用免费的Docker Hub服务来支付私有托pipe费用。

I0210 17:07:12.341120 9 slave.cpp:4999] Launching executor test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 with resources cpus(*):0.1; mem(*):32 in work directory '/tmp/mesos/slaves/379ed26c-465f-4b0f-90f9-d058ad6d028b-S0/frameworks/379ed26c-465f-4b0f-90f9-d058ad6d028b-0000/executors/test2.ba02dba1-d018-11e5-87cd-02420a013102/runs/ef4db108-dce3-45f6-b273-11db38289e24' I0210 17:07:12.341696 8 docker.cpp:735] No container info found, skipping launch I0210 17:07:12.341958 9 slave.cpp:1628] Queuing task 'test2.ba02dba1-d018-11e5-87cd-02420a013102' for executor 'test2.ba02dba1-d018-11e5-87cd-02420a013102' of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 E0210 17:07:12.342250 9 slave.cpp:3466] Container 'ef4db108-dce3-45f6-b273-11db38289e24' for executor 'test2.ba02dba1-d018-11e5-87cd-02420a013102' of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 failed to start: None of the enabled containerizers (docker) could create a container for the provided TaskInfo/ExecutorInfo message E0210 17:07:12.343215 9 slave.cpp:3537] Termination of executor 'test2.ba02dba1-d018-11e5-87cd-02420a013102' of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 failed: Unknown container: ef4db108-dce3-45f6-b273-11db38289e24 I0210 17:07:12.343487 9 slave.cpp:2762] Handling status update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 from @0.0.0.0:0 W0210 17:07:12.343763 11 docker.cpp:998] Ignoring updating unknown container: ef4db108-dce3-45f6-b273-11db38289e24 I0210 17:07:12.344077 10 status_update_manager.cpp:322] Received status update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 I0210 17:07:12.344272 10 status_update_manager.cpp:826] Checkpointing UPDATE for status update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 I0210 17:07:12.369632 10 slave.cpp:3087] Forwarding the update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 to master@192.168.8.101:5050 I0210 17:07:12.382553 8 status_update_manager.cpp:394] Received status update acknowledgement (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 I0210 17:07:12.382820 8 status_update_manager.cpp:826] Checkpointing ACK for status update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 I0210 17:07:12.414659 8 slave.cpp:3657] Cleaning up executor 'test2.ba02dba1-d018-11e5-87cd-02420a013102' of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000