>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.
e last email:
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0313 13:39:45.608578 258 fetcher.cpp:76] Fetching URI
'/usr/local/bin/thermos_executor.pex'
I0313 13:39:45.609048 258 fetcher.cpp:179] Copying resource from
'/usr/local/bin/thermos_executor.pex'
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
tion i've found possible and still generally
usable. (around 100MB with docker and some other tools i include)
root@s1:~# ls
/tmp/mesos/slaves/20150313-131712-1143806393-5050-6-S0/frameworks/20150306-112428-1177360825-5050-6-/executors/thermos-1426253925515-docker-test-devel-hello_docker-0-a90
ta) is running
> on ramdisk on these machines, it's the absolute minimal ubuntu "minbase"
> (debootstrapped) installation i've found possible and still generally
> usable. (around 100MB with docker and some other tools i include)
>
>
> root@s1:~# ls
&g
s 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
