Interface IP is incorrect and not found while starting Hazelcast in a dockerized environment for Confluence Data Center
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
While starting up Confluence Synchrony (collaborative editing) in a dockerized environment, you get the following error in the atlassian-synchrony.log:
ERROR [main] [com.hazelcast.instance.AddressPicker] [LOCAL] [confluence-<name>-Synchrony] [3.11.4] Hazelcast CANNOT start on this node. No matching network interface found.
When you view the <Confluence local home>/confluence.cfg.xml file, the network interface is set correctly under the _<confluence.cluster.interface>_ property, however the IP address of the interface is incorrect.
Environment
Confluence Data Center 7.1.1
Docker
Diagnosis
The Hazelcast service cannot find the IP or interface when starting and fails to start the synchrony service.
Cause
Docker uses 'Virtual Networks', networks that are independent and outside the scope of the host machine network interface unless setup otherwise. Virtual networks by default use the bridged driver.
Solution
If you plan on using the host machines network interface, switch the virtual network on docker to use the host driver.
If using host driver is not a viable option please refer to Configuring Hazelcast in Non-Orchestrated Docker Environments for some additional solutions.