Re: Question regarding docker containerizer

Thank you Guangya, that perfectly answers my doubt. On Sat, Feb 27, 2016 at 8:15 AM, Guangya Liu wrote: > The Docker Executor was also managed by Mesos itself, you can refer to > https://github.com/apache/mesos/blob/master/src/slave/containerizer/docker.cpp#L1197 > , the executor was managed by

Re: Question regarding docker containerizer

The Docker Executor was also managed by Mesos itself, you can refer to https://github.com/apache/mesos/blob/master/src/slave/containerizer/docker.cpp#L1197 , the executor was managed by mesos and mesos can set the default resources for the executor: https://github.com/apache/mesos/blob/master/src/s

Re: Question regarding docker containerizer

Actually the reason i asked this question is because i am unable to generate these warning messages by setting MEMORY < MIN_MEM and CPU < MIN_CPUS in case of docker containers started using marathon. https://github.com/apache/mesos/blob/4d4d7166414f0ebd8d5e40df34070446098a3c91/src/master/validatio

Re: Question regarding docker containerizer

Thank you Jie and Jojy for the help. On Fri, Feb 26, 2016 at 4:50 AM, Jojy Varghese wrote: > Hi Pradeep, > > The relevant code if you are interested is at : > > https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L3561 > > https://github.com/apache/mesos/blob/master/src/slave/slave.c

Re: Question regarding docker containerizer

Hi Pradeep, The relevant code if you are interested is at : https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L3561 https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L3672

Re: Question regarding docker containerizer

Yeah, that's the command task. Mesos run all tasks using some executor. If the user does not specify one (command task case), we will use the default mesos executor. On Thu, Feb 25, 2016 at 4:10 PM, Pradeep Chhetri < pradeep.chhetr...@gmail.com> wrote: > Hi Jie, > > I see executor_id as empty. Do

Re: Question regarding docker containerizer

Hi Jie, I see executor_id as empty. Does this means that it is running as task and there is no executor for it ? Although, in the ps output, I see mesos-slave is spawning a mesos-docker-executor which in turn spawning the docker command. Here is the detail of one of the marathon task: {"id": "log

Re: Question regarding docker containerizer

You can checkout the state.json endpoint on the master On Thu, Feb 25, 2016 at 3:53 PM, Pradeep Chhetri < pradeep.chhetr...@gmail.com> wrote: > Hello Jie, > > Thank you for the quick reply. Sorry for asking silly question. How can i > look for the taskinfo of a running container ? Can i see the T

Re: Question regarding docker containerizer

Hello Jie, Thank you for the quick reply. Sorry for asking silly question. How can i look for the taskinfo of a running container ? Can i see the TaskInfo details in the mesos master UI for a task? On Thu, Feb 25, 2016 at 10:52 PM, Jie Yu wrote: > You can take a look at the TaskInfo. If the Tas

Re: Question regarding docker containerizer

You can take a look at the TaskInfo. If the TaskInfo does not have ExecutorInfo set, then it's a task. Otherwise, Mesos will launch the executor and send the task to the executor. - Jie On Thu, Feb 25, 2016 at 2:50 PM, Pradeep Chhetri < pradeep.chhetr...@gmail.com> wrote: > Hello, > > From docke

Question regarding docker containerizer

Hello, >From docker containerizer documentation ( http://mesos.apache.org/documentation/latest/docker-containerizer/), *"Users can either launch a Docker image as a Task, or as an Executor."* How can i identify whether a docker container started by lets say marathon is running as a task or as an