Dan (Turk) Osborne
Dan (Turk) Osborne
@sargun I agree with that this is a problem that should be addressed in core Mesos, but [Avinash does not](https://issues.apache.org/jira/browse/MESOS-5325?focusedCommentId=15271498&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15271498). I have already made two suggestions to fix this -...
The behavior requested in this issue is that: With one Mesos-DNS configuration setting, Docker bridge tasks return the agent IP, and ip-per-container tasks return their `NetworkInfo.Ip`. @sargun I'm not sure...
Oh, I didn't notice the `containerip`/`agentip` in those requests. @sargun I don't believe this is a useful solution, as the logic of which of those two address to to use...
Good question. It is arguable whether it should be decided by core Mesos or decided at the service layer as we are discussing. On one hand, Mesos is reporting enough...
@sargun @jdef as discussed, let's add an experimental `"auto"` configuration to Mesos DNS which applies the following logic when returning entries: ``` if task.port_mappings or not task.network_info.ip_address: return agent_ip else:...
There's some info on it here, but its a tad outdated: https://github.com/mesosphere/net-modules/blob/master/docs/api.md#network-virtualizer-api
@Y4Rv1K and anyone else hitting this error: ``` INFO interface: error: undefined method `ipAddress=' for # undefined method `ipAddress=' for # INFO interface: Machine: error-exit ["VagrantPlugins::VSphere::Errors::VSphereError", "undefined method `ipAddress=' for...
@simsunny22 I encountered that when I set more nics in my customization spec than were configured on my template. To remedy that, try converting your template to a powered-off VM,...