Hi Javier, Thanks for the response. I am using mesos 0.20.0 and I have been using docker for a while on this machine.
I did actually find another email in the mailing list that gave me a solution for this although I don't fully understand it. I had to stop mesos and delete all of my previous docker containers (that I created before I started using mesos) using this command: docker rm `docker ps -qa` After starting mesos master and slave my scheduler is now being offered resources. I guess Mesos was seeing these containers as resources that had already been allocated? Thanks, Andy. -- Andy Grove VP Engineering CodeFutures Corporation On Fri, Sep 5, 2014 at 9:12 AM, Javier Ruiz Jiménez <[email protected]> wrote: > Hi Andy > > What version of Mesos are you using? > > Can you provide the mesos-slave log or what is printed after running > ./mesos-slave > --ip=127.0.0.1 ...? > > Is this the first time you run docker containers in that machine? > > Regards, > Javier > > > > > > Javier Ruiz Jiménez > Tecsisa > E: [email protected] > Tel: +34 91.182.04.71 (directo) > Tel: +34 91.445.21.15 (centralita) > Fax: +34 91.447.05.11 > http://www.tecsisa.com > > > 2014-09-05 17:06 GMT+02:00 Andy Grove <[email protected]>: > >> Hi, >> >> I'm very new to Mesos and am trying to get a simple Hello World running >> with Docker containers. >> >> I've taken a copy of the Java example framework code and have modified it >> to launch a docker task. >> >> If I run the mesos slave with the docker containerizer enabled using the >> following command then my scheduler doesn't get offered any resources. >> >> ./mesos-slave --ip=127.0.0.1 --master=127.0.0.1:5050 >> --containerizers=docker,mesos >> >> If I run without the --containerizers flag then my scheduler does get >> offered resources. >> >> Is there some extra configuration step that I am missing? >> >> Thanks, >> >> Andy. >> >> -- >> Andy Grove >> VP Engineering >> CodeFutures Corporation >> >> >> >
