You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "haosdent (JIRA)" <ji...@apache.org> on 2015/12/12 18:09:46 UTC

[jira] [Commented] (MESOS-4113) Docker Executor should not set container IP during bridged mode

    [ https://issues.apache.org/jira/browse/MESOS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054422#comment-15054422 ] 

haosdent commented on MESOS-4113:
---------------------------------

Framework should know task network mode, right? So for framework developers, could ignore it when don't need it. 
And I think fill ip_address in TaskStatus also necessary although container in bridge mode.
In some cases, for example, if user want to add containers ip to iptables in framework, so that user could get the NAT ip of container through TaskStatus.

> Docker Executor should not set container IP during bridged mode
> ---------------------------------------------------------------
>
>                 Key: MESOS-4113
>                 URL: https://issues.apache.org/jira/browse/MESOS-4113
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker
>    Affects Versions: 0.25.0, 0.26.0
>            Reporter: Sargun Dhillon
>              Labels: mesosphere
>
> The docker executor currently sets the IP address of the container into ContainerStatus.NetworkInfo.IPAddresses. This isn't a good thing, because during bridged mode execution, it makes it so that that IP address is useless, since it's behind the Docker NAT. I would like a flag that disables filling the IP address in, and allows it to fall back to the agent IP. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)