Re: Running Mesos agent with --containerizers=docker option on Mac

There is a JIRA tracking this https://issues.apache.org/jira/browse/MESOS-3821 , you can apply the patch https://reviews.apache.org/r/39939/ from @haosdent to have a try. Thanks, Guangya On Sat, Jun 4, 2016 at 8:12 AM, Bogdan Ghit wrote: > Hi all, > > I am trying to run an agent as follows on

Running Mesos agent with --containerizers=docker option on Mac

Hi all, I am trying to run an agent as follows on my local machine running MacOS: ./bin/mesos-agent.sh --master=127.0.0.1:5050 --work_dir=work --containerizers=docker. The error I get is: Failed to perform recovery: Failed to 'docker -H unix://var/run/docker.sock ps -a': exist status = exited wit

OSX 10.10.5 and mesos 0.28.1 -- 10 to 20 X difference in sleep() method compared to non mesos

Hi, We are running the following Java application and we are getting unreasonable deltas in the actual amount time slept. On linux the results are as expected 10, 11, 12 but mostly 10ms. Can you suggest any changes we can make or is this a known issue or a new issue to be investigated?

Re: Set LIBPROCESS_IP for frameworks launched with marathon

The reason I need to set LIBPROCESS_IP is because the slaves have 2 network interfaces, and the docker container is running in host networking mode. So libmesos doesn’t know which IP to advertise. The hostnames of the slaves are all resolvable. I have noticed that if I run a marathon app that