Hazelcast only binds to local interface

Summary

When running Bitbucket Server in a dockerised multi-node environment you may run into an issue where the nodes advertise their private networks to each other and thus refuse to let them join the cluster.

Environment

• Docker on multiple hosts

Steps to Reproduce

1. Configure Bitbucket server to run in a multi node environment inside docker on more than one host

Expected Results

Bitbucket server starts up and nodes join the cluster

Actual Results

Nodes do not join the cluster

Wrong bind request from [privateIP]:5701! This node is not requested endpoint: [publicIp]

Workaround

At present the best workaround is to setup a docker-overlay network
https://docs.docker.com/network/overlay/

Suggested Solution

Hazelcast has a solution to this by way of the configuration property
hazelcast.local.publicAddress but it is not exposed. Exposing this property should solve this problem.