Adding healtcheck in docker compose file caused the container to fail about docker-mariadb-cluster HOT 4 OPEN

Hi @yaakov-berkovitch,
I have an idea, but it has nothing to do with the healtcheck.
I was playing around and found that compose version 3 does not work with swarm mode. So at least I saw this message after docker-compose up:

WARNING: Some services (mariadb) use the 'deploy' key, which will be ignored. Compose does not support deploy configuration - use `docker stack deploy` to deploy to a swarm.

This mariadb-cluster image was especially designed to work with swarm mode. When doing the init_cluster stuff it tries to get the IPs of the other nodes. getent hosts tasks.$DB_SERVICE_NAME

This check does not return anything or when doing it here

CLUSTER_MEMBERS=`getent hosts tasks.$DB_SERVICE_NAME|awk '{print $1}'|tr '\n' ','`

it fails with exit code 2

Why does it work sometime and sometimes not?
Simple. Since you are working with docker-compose there is a containername created at each startup. This name consists of currentDirectory_ServiceName_NumberCurrentReplica. For the same service within a compose file this name does not change.
At the first initial start the container fails and exits. But the container still exists. The next docker-compose up does not initialize a brand new container, but starts the previous one, since the name according to the naming schema of compose is identical.
But this time the original docker-entrypoint.sh script from MariaDB finds an already installed database, since there already is a data directory present in the container. If this is the case the init scripts within /docker-entrypoint-initdb.d/* don't get executed and hence it cannot fail with this exit 2 error.

from docker-mariadb-cluster.

Thanks your answer.
I was probably not clear but I'm using the compose file together with the docker deploy --compose-file.
So the deployment is made in the swarm mode.
Also the exit code I got during deployment is also 2 and the issue is perhaps also related to getent.
But I cannot figure why the healthcheck instruction interfere with the launching of the container.

from docker-mariadb-cluster.

Same problem. I would like to make a health check that the server is running and fully replicated and ready to accept new requests.

from docker-mariadb-cluster.

Workaround:

Use https://github.com/colinmollenhour/mariadb-galera-swarm with included work healtcheck.

from docker-mariadb-cluster.