Hi Vinod - this is good news! Just the fact that I'm not barking up the
wrong tree and that indeed it is a known issue.
Cheers
Jim
On 11 June 2015 at 18:16, Vinod Kone vinodk...@gmail.com wrote:
On Thu, Jun 11, 2015 at 4:00 AM, James Vanns jvanns@gmail.com wrote:
I think I can
For what exactly? I thought that was for slave-master communication?
There is no problem there. Or are you suggesting that from inside the
running container I set at least LIBPROCESS_IP to the host IP rather than
the IP of eth0 the container sees? Won't that screw with the docker bridge
routing?
Looks like I share the same symptoms as this 'marathon inside container'
problem;
https://groups.google.com/d/topic/marathon-framework/aFIlv-VnF58/discussion
I guess that sheds some light on the subject ;)
On 11 June 2015 at 09:43, James Vanns jvanns@gmail.com wrote:
For what exactly? I
I think I can conclude then that this just won't work; one cannot run a
framework as a docker container using bridged networking. This is because a
POST to the MM that libprocess does on your framework's behalf, includes
the non-route-able private docker IP and that is what the MM well then try
to
On Thu, Jun 11, 2015 at 4:00 AM, James Vanns jvanns@gmail.com wrote:
I think I can conclude then that this just won't work; one cannot run a
framework as a docker container using bridged networking. This is because a
POST to the MM that libprocess does on your framework's behalf, includes
I believe you're correct Jim, if you set LIBPROCESS_IP=$HOST_IP libprocess will
try to bind to that address as well as announce it, which won't work inside a
bridged container.
We've been having a similar discussion on
https://github.com/wickman/pesos/issues/25.
--
Tom Arnfeld
On Jun 10, 2015, at 10:10 AM, James Vanns jvanns@gmail.com wrote:
Hi. When attempting to run my scheduler inside a docker container in
--net=bridge mode it never receives acknowledgement or a reply to that
request. However, it works fine in --net=host mode. It does not listen on any
Hi. When attempting to run my scheduler inside a docker container in
--net=bridge mode it never receives acknowledgement or a reply to that
request. However, it works fine in --net=host mode. It does not listen on
any port as a service so does not expose any.
The scheduler receives the mesos
8 matches
Mail list logo
