It's not a bug, it's a feature - http://mesosphere.github.io/mesos-dns/docs/configuration-parameters.html look at IPSources config
śr., 28.10.2015 o 15:59 użytkownik John Omernik <[email protected]> napisał: > If I rolled back mesos-dns to v0.2.0 (on the releases page) then it pulls > the right IP address.. (Mesos-dns version is the easiest of the three to > change) > > John > > On Wed, Oct 28, 2015 at 9:52 AM, John Omernik <[email protected]> wrote: > >> So, the issues that are listed appear to be resolved with marathon >> 0.11.1, and the mesos-dns issue is not listed at all. >> >> Note, I tried mesos-dns 0.3.0 and that has the same problem as 0.4.0. >> >> On Wed, Oct 28, 2015 at 9:46 AM, John Omernik <[email protected]> wrote: >> >>> I will check out those issues and report back. >>> >>> On Wed, Oct 28, 2015 at 9:42 AM, craig w <[email protected]> wrote: >>> >>>> I've had no issue with the following combination: >>>> >>>> MesosDNS 0.4.0 >>>> Marathon 0.11.0 >>>> Mesos 0.24.1 >>>> >>>> I've been waiting to upgrade to Mesos 0.25.0 because of issues >>>> mentioned in the mesos mailing list regarding Marathon 0.11.x and Mesos >>>> 0.25.0 >>>> >>>> On Wed, Oct 28, 2015 at 10:38 AM, John Omernik <[email protected]> >>>> wrote: >>>> >>>>> Hey all - >>>>> >>>>> I am cross posting this because it's a number of moving parts that >>>>> could be at issue here (Mesos, Mesos-dns, and/or Marathon). >>>>> >>>>> Basically: At the version combination in Subject, the IP that is >>>>> registered in mesos-dns for Docker containers running in Marathon is the >>>>> internal (container) IP address of the docker (in bridged mode) not the >>>>> nodes. This obviously causes issues. Note this doesn't happen when the >>>>> Marathon application is non-Docker. >>>>> >>>>> I was running Mesos-dns 0.4.0 on a cluster running Mesos 0.24.0 and >>>>> Marathon 0.10.0 and I upgraded to Mesos 0.25.0 and Marathon 0.11.1 and >>>>> noticed this behavior happening. >>>>> >>>>> I thought that was odd because I have another cluster that was running >>>>> Mesos 0.25.0 and Marathon 0.11.1 and it wasn't happening, until I realized >>>>> that I hadn't upgraded Mesos-dns lately, I upgraded to Mesos-dns 0.4.0 and >>>>> the problem started occurring. >>>>> >>>>> Is there a setting that I need to use the external IP of the >>>>> container? Is this issue known? Is there a workaround? This is pretty >>>>> major >>>>> for Docker running on Marathon and using Mesos-dns for service discovery. >>>>> >>>>> John Omernik >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> https://github.com/mindscratch >>>> https://www.google.com/+CraigWickesser >>>> https://twitter.com/mind_scratch >>>> https://twitter.com/craig_links >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "marathon-framework" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> >
