Why weren't Weaviate and db_postgres pulled when I pulled the image?

[shy20221121]

Self Checks

• 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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Why weren't Weaviate and db_postgres pulled when I pulled the image?

version : 1.11.3 docker deployment

2. Additional context or comments

No response

[dosubot[bot]]

Weaviate and db_postgres weren't pulled because they're defined in the docker-compose.yml under specific Docker Compose profiles—'weaviate' and 'postgresql'—which aren't enabled by default. When you run docker compose up -d, only the default profile services are started and their images pulled. To include Weaviate and db_postgres, you need to explicitly enable their profiles with:

docker compose --profile postgresql --profile weaviate up -d

This setup gives you flexibility to choose which database and vector store to run. If you want Dify to use Weaviate, set VECTOR_STORE=weaviate in your .env file, but you still need to start the container using the profile command above. The same applies for db_postgres and its related environment variables. More details are in the compose file and docs discussion.

To reply, just mention @dosu.

---

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

   

[shy20221121]

Weaviate and db_postgres weren't pulled because they're defined in the docker-compose.yml under specific Docker Compose profiles—'weaviate' and 'postgresql'—which aren't enabled by default. When you run docker compose up -d, only the default profile services are started and their images pulled. To include Weaviate and db_postgres, you need to explicitly enable their profiles with:

docker compose --profile postgresql --profile weaviate up -d

This setup gives you flexibility to choose which database and vector store to run. If you want Dify to use Weaviate, set VECTOR_STORE=weaviate in your .env file, but you still need to start the container using the profile command above. The same applies for db_postgres and its related environment variables. More details are in the compose file and docs discussion.

To reply, just mention @dosu.

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

   

@dosu

Is this a change in version 1.11.3? Because when I used 1.11.0 before, Weaviate and db_postgres could still be automatically started.

[dosubot[bot]]

Yes, this is a change in behavior. In version 1.11.3, both Weaviate and db_postgres are defined under Docker Compose profiles, so they are not started or pulled by default—you have to explicitly enable their profiles when running Docker Compose. This setup gives you more flexibility but requires the extra step. In earlier versions like 1.11.0, these services could be started automatically without specifying profiles, so the change likely happened between those versions. You can see the current profile-based setup in the docker-compose.yaml for 1.11.3.

To reply, just mention @dosu.

---

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