Ok I think I have possible solution... Based on:
https://docs.mesosphere.com/1.11/networking/DNS/
The container IP is available at:
.marathon.containerip.dcos.thisdcos.directory also
according to the docs this will return the proper I.P if in container or
bridge mode. Currently I only have
Maybe allow amore general SPI that scans I.Ps based on wildcard. For example:
9.x.x.*?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, on that note I will try the mesos framework. And a native IPFinder DC/OS
would be appreciated (not swarm).
>From what I see some Hazelcast folks have done something similar...
This uses marathon: https://github.com/phaneesh/hazelcast-marathon-discovery
This seems to just use the container
I guess we should update the documentation.
Does this suggest that an IpFinder for Docker Swarm (much like the one for
Kubernetes) would be useful?
Regards,
Stephen
> On 20 Dec 2018, at 14:13, Ilya Kasnacheev wrote:
>
> Hello!
>
> #1 you should use
Hello!
#1 you should use ./libs/optional/ignite-mesos/ignite-mesos-.jar -
looks like it's THE full JAR.
Regards,
--
Ilya Kasnacheev
чт, 20 дек. 2018 г. в 02:09, javadevmtl :
> Hi, from what I have tried and read it seems that you need host network for
> docker to run Ignite and overlay
Hi, from what I have tried and read it seems that you need host network for
docker to run Ignite and overlay networks cause issues...
I'm using DC/OS and I can technically maybe try the mesos deployment, but
not sure how new or old that framework is.
#1 the docs indicate to use:
