Skip to content

LLM-Driven Extraction of Unstructured Data — Built for API Deployments & ETL Pipeline Workflows

[MISC] Wait for minio-bootstrap to complete instead of racing it (#2247)

Chandrasekharan Ma4af5e2d623d
diff --git a/docker/docker-compose.yaml b/docker/docker-compose.yaml
index 9a8db90af..10a7b4e5d 100644
--- a/docker/docker-compose.yaml
+++ b/docker/docker-compose.yaml
@@ -26,14 +26,24 @@ services:
env_file:
- ../backend/.env
depends_on:
- - db
- - redis
- - rabbitmq
- - reverse-proxy
- - minio
- - minio-bootstrap
- - platform-service
- - x2text-service
+ db:
+ condition: service_started
+ redis:
+ condition: service_started
+ rabbitmq:
+ condition: service_started
+ reverse-proxy:
+ condition: service_started
+ minio:
+ condition: service_started
+ # One-shot bucket setup. Waiting for completion keeps `up --wait` from
+ # treating its exit as a stack failure.
+ minio-bootstrap:
+ condition: service_completed_successfully
+ platform-service:
+ condition: service_started
+ x2text-service:
+ condition: service_started
volumes:
- prompt_studio_data:/app/prompt-studio-data
- ./workflow_data:/data