Hi John, It looks like a Marathon json, and I think possibly that it wasn't able to pull or launch the image (test:first).
Currently the sandbox stdout/stderr only redirect log from a running container, so if the container wasn't able to launch at all then it won't be in the task logs. However, we do log the launch error in the slave log, so if you search in your slave log around your TASK_FAILED message you should see it (Failed to launch container: .......) Tim On Sun, Sep 7, 2014 at 8:05 PM, John Omernik <[email protected]> wrote: > I am testing some containers, I have one running, so I know things are > technically working (at least partially) however, when I am testing a > container made by a friend, it fails. I am ok with failure :) However, I am > at a loss on how to troubleshoot. Both standard err and standard out in > the sandbox link in the gui of the failed attempt show 0 bytes (and > obviously no data). > > I am ok rooting around to troubleshoot, but I need some logs. Note, this > is separate from my other issue I've posted about with lack of logs. Other > frameworks logs are appearing while I am not getting any data from > specifically docker here. In the other issue, when it's happening, no > frameworks show any logs. > > Thanks! > > > Here is my json > > { > > "container": { > > "type": "DOCKER", > > "docker": { > > "image": "test:first" > > } > > }, > > "id": "test", > > "instances": "1", > > "cpus": "0.25", > > "mem": "64", > > "cmd":"bootstrap.sh" > > } >
