Re: Incompleteness of ContainerInfo.DockerInfo.DockerInfo ?

Hello, Apparently Marathon does not support portMapping with host IP address either. Fragment from https://mesosphere.github.io/marathon/docs/rest-api.html#post-v2-apps "portMappings": [ { "containerPort": 8080, "hostPort": 0,

Re: ContainerId in TaskStatus message: can't find update in mesos.proto

>From what I read in the ticket, What's done is "adding the output of `docker output` to the `data` field of TaskStatus message when a task is in TASK_RUNNING state', so the related protobuf field is TaskStatus.data, not a specific 'containerid' field. See

Re: Update on MesosCon 2016 Planning

I am curious to know that as well, about the reason for this change. We could benefit alot by staying open as it has been. On Mon, Dec 21, 2015 at 1:30 PM, Arunabha Ghosh wrote: > > > On Sun, Dec 20, 2015 at 12:00 AM, Dave Lester wrote: > >>

Re: Incompleteness of ContainerInfo.DockerInfo.DockerInfo ?

Viktor, you are correct that Mesos' DockerInfo doesn't have explicit support for the ip:hostPort:containerPort format, but you can use the DockerInfo.parameters field to pass arbitrary parameters to the docker CLI. https://github.com/apache/mesos/blob/0.26.0/include/mesos/mesos.proto#L1482

ContainerId in TaskStatus message: can't find update in mesos.proto

Hi, mesos .023 added ContainerId in TaskStatus message as per: https://issues.apache.org/jira/browse/MESOS-2191 However, I do not see any related modification in mesos.proto [0] Am I missing something? As such is python client including the modification? [0]

Question on adding commit hook to enforce leading whitespace in comments

As a newbie to Apache mesos project I have run into issues of missing whitespace in comments during reviews. Hence, wanted to see if we can add a commit hook to detect this style violation and enforce it by not allowing the commit to go through. Accordingly have created a JIRA (

Re: Question on adding commit hook to enforce leading whitespace in comments

a) +1 to new cpplint rule for single space after "//" b) I'd vote for single-space before the comment too. I haven't seen anybody do double-spaces in Mesos. The only exception to the single-space rule would be places where we try to align trailing comments. Not sure if we want to continue to allow

Re: Update on MesosCon 2016 Planning

Have no fear: the spirit of MesosCon has not changed, nor has the conference's organization become less open. A key difference is that the event chair is now a set of co-chairs (a system we successfully adopted for MesosCon Europe in October). By moving beyond the previous structure where I was

Re: ContainerId in TaskStatus message: can't find update in mesos.proto

On 12/21/2015 03:08 PM, Shuai Lin wrote: > From what I read in the ticket, What's done is "adding the output of > `docker output` to the `data` field of TaskStatus message when a task is in > TASK_RUNNING state', so the related protobuf field is TaskStatus.data, not > a specific 'containerid'