When starting the middleware using `middleware.env`, the database container is not pulled.

[ACAne0320]

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

main

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Execute docker compose --env-file middleware.env -f docker-compose.middleware.yaml -p dify up -d

In #28188 , only the .env.example file includes the COMPOSE_PROFILES=${DB_TYPE:-postgresql} parameter.
This prevents middleware.env from reading the correct profile parameters, resulting in the database container failing to be pulled.

✔️ Expected Behavior

All middleware containers should start normally.

❌ Actual Behavior

The database container has not been pulled.

[dosubot]

The database container isn't being pulled because the middleware.env file does not set the COMPOSE_PROFILES environment variable. Docker Compose uses profiles to determine which services to start, and the database containers in docker-compose.middleware.yaml are tied to profiles like postgresql or mysql. The .env.example file includes COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-postgresql}, which activates the necessary profiles for both the vector store and the database type, but this is missing from middleware.env source.

To fix this, add the following line to your middleware.env file (adjust values as needed for your setup):

COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-postgresql}

This will ensure Docker Compose activates the correct profile and pulls/starts the database container as expected source.

It may also help to update documentation or provide a template middleware.env with this variable included to prevent future confusion.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}