The majority of the resolution to this happened on irc, #aurora / freenode,
thanks to Steve :)
i'm including it here "for logging" / searchability.
We're running all of mesos, aurora, thermos-observer, zookeeper and such in
docker containers, mesos-slave in a container managing other containers on
I just noticed this line in your previous email:
"Everything's included in the image, that's the image i'm running mesos-master,
aurora, and mesos-slave from."
Are you saying you're running the slave inside a docker container? If so,
mesos does not support running docker containers from inside an
Thanks for the reply!
The only files i find in the workdir is stderr, stdout and
thermos_executor.pex
Nothing is cleaning the tmp directory, everything (except /data) is running
on ramdisk on these machines, it's the absolute minimal ubuntu "minbase"
(debootstrapped) installation i've found possib
When the task launches, a sandbox directory is created, in the above e-mail
it
was
/tmp/mesos/slaves/20150313-131712-1143806393-5050-6-S0/frameworks/20150306-112428-1177360825-5050-6-/executors/thermos-1426253925515-docker-test-devel-hello_docker-0-a9011a74-c2a2-4cb7-b402-d383fde58c41/runs/e53
I wasn't subscribed to the mailing-list (I'm subscribed now though) so
i'm sorry if this reply ends up in the wrong place..
>From the mesos slave log it looks like the executor is failing. Most
likely the issue is your image doesn't have the native libraries needed to
run it. The next step would
>From the mesos slave log it looks like the executor is failing. Most
likely the issue is your image doesn't have the native libraries needed to
run it. The next step would be to look in the sandbox for a failed run
(you can find the path in the slave logs) and look at the stderr log for
errors.
