add health checks to rabbit and postgres to ensure they are healthy before augur starts.

This avoids some race conditions with the startup process that could create issues, especially on first initialization.

Co-Authored-By: guptapratykshh <pratykshgupta9999@gmail.com>
Co-Authored-By: Sukuna0007Abhi <appsonly310@gmail.com>
Signed-off-by: Adrian Edwards <adredwar@redhat.com>

Author: 3 people

docker-compose.yml

@@ -14,6 +14,15 @@ services:
       - augurpostgres:/var/lib/postgresql/data
     networks:
       - augur
+    healthcheck:
+      test:
+        [
+          "CMD-SHELL",
+          "pg_isready -U ${AUGUR_DB_USER:-augur} -d ${AUGUR_DB_NAME:-augur}",
+        ]
+      interval: 10s
+      timeout: 5s
+      retries: 5
 
   redis:
     image: "redis:alpine"
@@ -45,6 +54,12 @@ services:
       - RABBIT_MQ_DEFAULT_VHOST=${AUGUR_RABBITMQ_VHOST:-augur_vhost}
     networks:
       - augur
+    healthcheck:
+      test: ["CMD", "rabbitmq-diagnostics", "ping"]
+      interval: 10s
+      timeout: 5s
+      retries: 10
+      start_period: 10s
 
   augur:
     image: augur-new:latest
@@ -78,10 +93,14 @@ services:
       - CACHE_LOCKDIR=/cache
       - CELERYBEAT_SCHEDULE_DB=/tmp/celerybeat-schedule.db
     depends_on:
-      - augur-db
-      - redis
-      - augur-keyman
-      - rabbitmq
+      augur-db:
+        condition: service_healthy
+      redis:
+        condition: service_started
+      augur-keyman:
+        condition: service_started
+      rabbitmq:
+        condition: service_healthy
     networks:
       - augur
     user: 2345:2345  # Run as an arbitrary non-root user