docker compose up -d fails: minio not started but FILE_STORE_BACKEND defaults to s3

[Opeple0627]

Description

Following the official local Docker deployment docs, running docker compose up -d causes the API server to crash immediately with:

botocore.exceptions.EndpointConnectionError: Could not connect to the endpoint URL: "http://minio:9000/onyx-file-store-bucket"
ERROR: Application startup failed. Exiting.

Root Cause

docker-compose.yml has a contradiction:

• api_server defaults to FILE_STORE_BACKEND=s3 (line 79), which requires minio
• The minio service is gated behind profiles: ["s3-filestore"] (line 523), so it is never started by the default docker compose up -d command

Even though minio is listed as required: false in the api_server depends_on, the API server still crashes when it cannot connect to the S3 endpoint at startup.

Steps to Reproduce

git clone --depth 1 https://github.com/onyx-dot-app/onyx.git
cd onyx/deployment/docker_compose
docker compose up -d
docker logs onyx-api_server-1

Expected Behavior

The default docker compose up -d command should result in a working deployment as documented.

Workaround

docker compose --profile s3-filestore up -d

Suggested Fix

Either:

1. Remove profiles: ["s3-filestore"] from the minio service so it starts by default, or
2. Change the default FILE_STORE_BACKEND to a local/non-S3 option when minio is not running

Environment

• OS: Ubuntu 24.04.4 (VMware)
• Docker version: latest