docker-compose.middleware.yaml does not start the Weaviate container by default

[hwzhuhao]

Self Checks

• 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 (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

main

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1.docker-compose -f docker-compose.middleware.yaml up -d

✔️ Expected Behavior

db,redis,sandbox,ssrf_proxy,weaviate is started

❌ Actual Behavior

only db,redis,sandbox,ssrf_proxy is started

[dosubot]

The docker-compose.middleware.yaml file does not start the Weaviate container by default because the Weaviate service is associated with a profile named weaviate. Docker Compose profiles allow you to selectively enable services. By default, services with profiles are not started unless explicitly specified.

To start the Weaviate container, you need to include the profile in your docker-compose command:

docker-compose -f docker-compose.middleware.yaml --profile weaviate up -d

This will ensure that the Weaviate service is started along with the other services ^[1].

To continue talking to Dosu, mention @dosu.