Hello We're testing out Ignite and are running them in Docker as well. It's a bit tricky to get to work. Keep in mind that referencing localhost inside a docker container is pointing them against their internal address. Not the host address of your machine. So that's why they aren't discovering eachother.
There are some options I can suggest: 1. Create a docker network and attach your containers to this network. Then you can add them to your addresses list by their container name. This is what we are currently doing. 2. Run them with --network host. Then you can use "localhost" as this will now be your host machine. In my opinion it kinda defeats the point of running it on Docker, but this is where I have had the best results. Best regards Niels Elkjær Ejrnæs Software Developer R&D -----Original Message----- From: vitalys <[email protected]> Sent: 8. august 2019 20:22 To: [email protected] Subject: RE: Running Ignite Cluster using Docker containers <property name="discoverySpi"> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> <property name="ipFinder"> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> <property name="addresses"> <list> <value>localhost:47500..47504</value> </list> </property> </bean> </property> </bean> </property> -- Sent from: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ignite-users.70518.x6.nabble.com%2F&data=02%7C01%7CNiels.Ejrnaes%40enghouse.com%7C30bb112adffb4afedc3a08d71c2d558e%7C427e40023c0240489e280eba58b331f4%7C1%7C1%7C637008853347767016&sdata=42KDcTU9%2FS%2ButBA7qRkPgeW%2BKo1zfP1N1zo4bmXgzBc%3D&reserved=0
