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
