[bitnami/redis-cluster] BUG: not working with healthcheck

[apachler]

Name and Version

bitnami/redis-cluster:7.2

What architecture are you using?

amd64

What steps will reproduce the bug?

Activating HEALTHCHECK in Docker Compose will stop container from working.

    healthcheck:
      test: ["CMD", "redis-cli", "ping"]
      interval: 10s
      timeout: 30s
      retries: 10
      start_period: 30s

What is the expected behavior?

Container is starting and working as expected.

What do you see instead?

The container's initialization stops at Setting Redis config file or while Changing old IP.

redis-cluster 07:37:14.77 INFO  ==>
redis-cluster 07:37:14.77 INFO  ==> Welcome to the Bitnami redis-cluster container
redis-cluster 07:37:14.77 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
redis-cluster 07:37:14.78 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
redis-cluster 07:37:14.78 INFO  ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
redis-cluster 07:37:14.78 INFO  ==>
redis-cluster 07:37:14.79 INFO  ==> ** Starting Redis setup **
redis-cluster 07:37:14.82 INFO  ==> Initializing Redis
redis-cluster 07:37:14.86 INFO  ==> Setting Redis config file
redis-cluster 07:37:14.99 INFO  ==> Changing old IP xxx by the new one yyy
redis-cluster 07:39:31.31 INFO  ==>

[javsalgar]

Hi,

Maybe the startup process is slower. Could you try increasing the number of retries? Also, could you try setting the BITNAMI_DEBUG=true environment variable?

[apachler]

Thanks for answering. I already have increased the retries to 1000. The container is not killed but did not finish startup.
Sure, i will give the BITNAMI_DEBUG=true env var a try and report back ...

[apachler]

Started the container with debug enabled with following logs

redis-cluster 08:29:37.85 INFO  ==>
redis-cluster 08:29:37.85 INFO  ==> Welcome to the Bitnami redis-cluster container
redis-cluster 08:29:37.86 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
redis-cluster 08:29:37.86 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
redis-cluster 08:29:37.86 INFO  ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
redis-cluster 08:29:37.86 INFO  ==>
redis-cluster 08:29:37.87 DEBUG ==> Copying files from /opt/bitnami/redis/etc.default to /opt/bitnami/redis/etc
redis-cluster 08:29:37.88 INFO  ==> ** Starting Redis setup **
redis-cluster 08:29:37.91 DEBUG ==> Validating settings in REDIS_* env vars..
redis-cluster 08:29:37.92 INFO  ==> Initializing Redis
redis-cluster 08:29:37.93 DEBUG ==> Ensuring expected directories/files exist
redis-cluster 08:29:37.96 INFO  ==> Setting Redis config file

It seems that the container is not able to finish initialization as soon as a healthcheck is defined...

[javsalgar]

Hi,

This is strange. This is the readiness command we execute in our side. But it's true that we provide an initialDelay, which would explain that there are no conflicts.

bitnami/charts@f499109

[apachler]

Ok, so is there any chance to get that fixed?