Re: Docker executor issue

Hi Vinod, The documentation actually already mentions this, that if a ExecutorInfo is set in the TaskInfo then it is expected to be a Mesos Executor and it is expected to be registering with the slave. Tim On Tue, Sep 30, 2014 at 11:42 AM, Vinod Kone wrote: > Tim, mind updating the documentati

Re: Docker executor issue

Tim, mind updating the documentation to make sure others don't fall into the same trap? On Tue, Sep 30, 2014 at 11:38 AM, Tim Chen wrote: > Hi Andy, > > Good catch, I also missed that as I was just looking at the Docker > confi

Re: Docker executor issue

Hi Andy, Good catch, I also missed that as I was just looking at the Docker configurations. You'll set the Executor when you have an custom executor. Let us know if you have any other problems. Tim On Tue, Sep 30, 2014 at 11:02 AM, Andy Grove wrote: > OK. So I figured out the issue with this

Re: Docker executor issue

from mesospheres.io, it is recommended you set up the timeout as Vinod mentioned earlier to be 5 mins. -Luyi. On Tue, Sep 30, 2014 at 11:02 AM, Andy Grove wrote: > OK. So I figured out the issue with this and it was my misunderstanding of > executors and tasks. > > My task info had: > > .se

Re: Docker executor issue

OK. So I figured out the issue with this and it was my misunderstanding of executors and tasks. My task info had: .setExecutor(Protos.ExecutorInfo.newBuilder(executor)) I should have had this: .setContainer(containerInfoBuilder) .setCommand(Protos.CommandInfo.newBuilder(

Re: Docker executor issue

Hi Tim, Thanks for helping with this. I am running mesos-master and mesos-slave natively on the same host (my desktop). The only container in use is the one being launched by the mesos-slave. I will try your suggestion of running a simple command next. Here is the output from the slave from this

Re: Docker executor issue

Hi Andy, You don't need to specifiy -d as the docker containerizer will set it for you since we run all docker images detached. It seems like the executor just simply can't register with the slave. Can you try just running a simple command without Docker that takes longer than the executor regist

Re: Docker executor issue

I'll let Tim Chen help you out here since he has more context. Some slave logs around the failed container launch would be helpful. On Mon, Sep 29, 2014 at 5:03 PM, Andy Grove wrote: > Ignore my comment about docker run not returning. That is incorrect. > > Thanks, > > Andy. > > -- > Andy Grove

Re: Docker executor issue

Ignore my comment about docker run not returning. That is incorrect. Thanks, Andy. -- Andy Grove VP Engineering CodeFutures Corporation On Mon, Sep 29, 2014 at 5:59 PM, Andy Grove wrote: > Hi Vinod, > > Thanks for the quick response but the image is already on the slave and I > see the cont

Re: Docker executor issue

Hi Vinod, Thanks for the quick response but the image is already on the slave and I see the container being launched almost immediately when my framework starts (within 1-2 seconds). If I keep running docker ps, this is the last output I see before the container is killed: $ docker ps CONTAINER I

Re: Docker executor issue

Trying increasing the executor registration timeout on the slave (--executor_registration_timeout) to give docker more time to do a pull of the image. On Mon, Sep 29, 2014 at 4:41 PM, Andy Grove wrote: > Hi, > > I've working on a prototype Mesos framework to launch docker containers. > I'm getti

Docker executor issue

Hi, I've working on a prototype Mesos framework to launch docker containers. I'm getting as far as seeing my container start up but after one minute if gets killed due to: Terminating executor default of framework 20140929-155916-16777343-5050-2708-0004 because it did not register within 1mins H