Provided that I know close to nothing about CoreOS (and very little about
docker itself) usually the 127 exit code is for a "not found" binary - are
you sure that `docker` is in the PATH of the user/process running the Mesos
agent?
Much longer shot - but worth a try: look into the permissions arou
I did try removing the /proc and adding just pid=host but still no dice with
that. Need to have a deeper dig into the docker 1.9 changelog. Will post back
if I find anything.
Thanks,
Graham.
On 31 Dec 2015, at 20:27, Tim Chen
mailto:t...@mesosphere.io>> wrote:
I don't think you need to mount
I don't think you need to mount in /proc if you have --pid=host already,
can you try that?
Tim
On Thu, Dec 31, 2015 at 4:16 AM, Taylor, Graham <
graham.x.tay...@capgemini.com> wrote:
> Hey folks,
> I’m trying to get Mesos slave up and running in a docker container on
> CoreOS. I’ve successfully
Hey folks,
I’m trying to get Mesos slave up and running in a docker container on CoreOS.
I’ve successfully got the master up and running but anytime I start the slave
container I receive the following error -
Failed to create a containerizer: Could not create DockerContainerizer: Failed
to crea
Good idea to get data locality for non distributed apps but spark driver
will distribute info to workers so it may result in all workers connecting
to instance on the same node as the driver.
I will do some test...
Le 31 déc. 2015 1:26 AM, "Shuai Lin" a écrit :
> What about specifying all non-l
Hi
Happy new year!
Current resources offering when master performs allocation is
coarse-grained, i.e. allocating the entire unused resources on slave to
one framework on each iteration. It’s unable for framework to specify
the unit of its requested resource, and also after the offering,
unne
6 matches
Mail list logo
