{"action":"created","issue":{"url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/426","repository_url":"https://api.github.com/repos/mesosphere/mesos-dns","labels_url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/426/labels{/name}","comments_url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/426/comments","events_url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/426/events","html_url":"https://github.com/mesosphere/mesos-dns/issues/426","id":155080131,"number":426,"title":"Distinguish between routable NetworkInfo and unroutable NetworkInfo","user":{"login":"djosborne","id":3444362,"avatar_url":"https://avatars.githubusercontent.com/u/3444362?v=3","gravatar_id":"","url":"https://api.github.com/users/djosborne","html_url":"https://github.com/djosborne","followers_url":"https://api.github.com/users/djosborne/followers","following_url":"https://api.github.com/users/djosborne/following{/other_user}","gists_url":"https://api.github.com/users/djosborne/gists{/gist_id}","starred_url":"https://api.github.com/users/djosborne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djosborne/subscriptions","organizations_url":"https://api.github.com/users/djosborne/orgs","repos_url":"https://api.github.com/users/djosborne/repos","events_url":"https://api.github.com/users/djosborne/events{/privacy}","received_events_url":"https://api.github.com/users/djosborne/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2016-05-16T17:38:04Z","updated_at":"2016-06-03T20:49:06Z","closed_at":null,"body":"Mesos DNS' own documentation describes this issue:\r\n\r\n>If you choose to use Mesos-DNS with Docker, with a version of Mesos after 0.25, be aware that there are some caveats. By default the Docker executor publishes the IP of the Docker container into the NetworkInfo field. Unfortunately, unless you're running some kind of SDN solution, bridged, or host networking with Docker, this can prove to make the containers unreachable.\r\n>\r\n>The default configuration that Mesos-DNS ships with in config.json.sample omits netinfo from the sources. The default options if you omit this field from the configuration includes netinfo. If you have trouble with Docker, ensure you check the IPSources field to omit netinfo.\r\n\r\nThis unfortunately means that IP-per-container tasks can't be used alongside standard Mesos tasks without breaking DNS resolution for one or the other. This makes it very difficult to introduce any limited IP-per-container support without breaking networking for standard tasks. **This will affect CNI as well, when it is introduced in Mesos 0.29.**\r\n\r\n[I raised this problem in the Mesos JIRA, but it has been brought up that this is really a service discovery issue, as Mesos is reporting information as expected](https://issues.apache.org/jira/browse/MESOS-5325)\r\n\r\nTherefore, I poropose that, when Mesos DNS is configured to prefer networkinfo, arbitrarily skip it when resolving Docker Bridge Tasks, continuing to the next \"`IPSources`\" field instead.\r\n"},"comment":{"url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/comments/223690845","html_url":"https://github.com/mesosphere/mesos-dns/issues/426#issuecomment-223690845","issue_url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/426","id":223690845,"user":{"login":"djosborne","id":3444362,"avatar_url":"https://avatars.githubusercontent.com/u/3444362?v=3","gravatar_id":"","url":"https://api.github.com/users/djosborne","html_url":"https://github.com/djosborne","followers_url":"https://api.github.com/users/djosborne/followers","following_url":"https://api.github.com/users/djosborne/following{/other_user}","gists_url":"https://api.github.com/users/djosborne/gists{/gist_id}","starred_url":"https://api.github.com/users/djosborne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djosborne/subscriptions","organizations_url":"https://api.github.com/users/djosborne/orgs","repos_url":"https://api.github.com/users/djosborne/repos","events_url":"https://api.github.com/users/djosborne/events{/privacy}","received_events_url":"https://api.github.com/users/djosborne/received_events","type":"User","site_admin":false},"created_at":"2016-06-03T20:49:06Z","updated_at":"2016-06-03T20:49:06Z","body":"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 information for Service Discovery services to tell which address the container should be reachable on (as I mentioned in my last comment). On the other hand, maybe that calculation should already be done in core Mesos. \r\n\r\nShall we continue / close out that discussion on [the Jira issue](https://issues.apache.org/jira/browse/MESOS-5325) before implementing  it here at the service layer?"}}
{"actor":{"display_login":"djosborne"}}