langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

when set VECTOR_STORE: ${VECTOR_STORE:-qdrant} not working #4349

New Issue
Closed
opened 2026-02-21 18:05:58 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:05:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @autherlj on GitHub (Jun 30, 2024).

Originally assigned to: @guchenhe on GitHub.

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).
  • 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.12-fix1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1.cp middleware.env.example middleware.env
2.set up VECTOR_STORE: ${VECTOR_STORE:-qdrant}
3.docker compose up -d
4.qdrant images not pulling
5.
image

✔️ Expected Behavior

qdrant container should be working

❌ Actual Behavior

No response

Originally created by @autherlj on GitHub (Jun 30, 2024). Originally assigned to: @guchenhe on GitHub. ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.12-fix1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1.cp middleware.env.example middleware.env 2.set up VECTOR_STORE: ${VECTOR_STORE:-qdrant} 3.docker compose up -d 4.qdrant images not pulling 5. ![image](https://github.com/langgenius/dify/assets/30717333/93c08e5a-ed33-4ab9-a5be-d2d9c9844549) ### ✔️ Expected Behavior qdrant container should be working ### ❌ Actual Behavior _No response_
yindo added the 👻 feat:rag label 2026-02-21 18:05:58 -05:00
yindo closed this issue 2026-02-21 18:05:58 -05:00
yindo commented 2026-02-21 18:05:58 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 30, 2024):

@autherlj Hello there! I'm here to assist you with any bugs, questions, or contributions you may have.

To resolve the issue with the Qdrant container not being pulled and running properly, ensure the following steps are correctly implemented:

  1. Uncomment the Qdrant Service in docker-compose.yaml:
    Make sure the Qdrant service is uncommented in your docker-compose.yaml file:

    services:
  qdrant:
    image: langgenius/qdrant:v1.7.3
    restart: always
    volumes:
      - ./volumes/qdrant:/qdrant/storage
    environment:
      QDRANT_API_KEY: 'difyai123456'
    ports:
      - "6333:6333"
      - "6334:6334"

  2. Set the VECTOR_STORE Environment Variable:
    Ensure the VECTOR_STORE environment variable is set to qdrant in the middleware.env file:

    VECTOR_STORE=qdrant

  3. Set the QDRANT_API_KEY and QDRANT_URL:
    Ensure the QDRANT_API_KEY and QDRANT_URL are correctly set in the middleware.env file:

    QDRANT_API_KEY=difyai123456
QDRANT_URL=http://qdrant:6333

  4. Check Service Dependencies:
    Ensure that the db and redis services are running before starting the Qdrant service. The depends_on directive in the docker-compose.yaml file should ensure this:

    depends_on:
  - db
  - redis

  5. Start Docker Compose:
    After making these changes, bring up the Docker services:

    docker compose up -d

By following these steps, the Qdrant container should be pulled and run properly in your self-hosted Docker setup for Dify version 0.6.12-fix1 [1][2][3][4].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 30, 2024): <!-- Greeting --> @autherlj Hello there! I'm here to assist you with any bugs, questions, or contributions you may have. <!-- Answer --> To resolve the issue with the Qdrant container not being pulled and running properly, ensure the following steps are correctly implemented: 1. **Uncomment the Qdrant Service in `docker-compose.yaml`**: Make sure the Qdrant service is uncommented in your `docker-compose.yaml` file: ```yaml services: qdrant: image: langgenius/qdrant:v1.7.3 restart: always volumes: - ./volumes/qdrant:/qdrant/storage environment: QDRANT_API_KEY: 'difyai123456' ports: - "6333:6333" - "6334:6334" ``` 2. **Set the `VECTOR_STORE` Environment Variable**: Ensure the `VECTOR_STORE` environment variable is set to `qdrant` in the `middleware.env` file: ```env VECTOR_STORE=qdrant ``` 3. **Set the `QDRANT_API_KEY` and `QDRANT_URL`**: Ensure the `QDRANT_API_KEY` and `QDRANT_URL` are correctly set in the `middleware.env` file: ```env QDRANT_API_KEY=difyai123456 QDRANT_URL=http://qdrant:6333 ``` 4. **Check Service Dependencies**: Ensure that the `db` and `redis` services are running before starting the Qdrant service. The `depends_on` directive in the `docker-compose.yaml` file should ensure this: ```yaml depends_on: - db - redis ``` 5. **Start Docker Compose**: After making these changes, bring up the Docker services: ```sh docker compose up -d ``` By following these steps, the Qdrant container should be pulled and run properly in your self-hosted Docker setup for Dify version 0.6.12-fix1 <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker-legacy/docker-compose.yaml)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/middleware.env.example)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/docker-legacy/docker-compose.qdrant.yaml)</sup><sup>[[4]](https://github.com/langgenius/dify/blob/main/docker/.env.example)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:05:58 -05:00
Author
Owner
Copy Link
Copy Source

@guchenhe commented on GitHub (Jul 1, 2024):

Hi @autherlj, thank you for the feedback, docker-compose.middleware.yaml is intended to facilitate the development of the frontend and backend of Dify, so you shouldn't need to modify the vector database as much. Apologies that the previous configurations and comments may have given the misleading conception that the vector db is configurable within the middleware services. I've since removed these. If you'd like to swap out weaviate for qdrant nevertheless, consider starting the services directly with something like docker compose -f docker/docker-compose.middleware.yaml -f docker/docker-compose.yaml up -d db redis sandbox ssrf_proxy qdrant

Hope this helps!

@guchenhe commented on GitHub (Jul 1, 2024): Hi @autherlj, thank you for the feedback, `docker-compose.middleware.yaml` is intended to facilitate the development of the frontend and backend of Dify, so you shouldn't need to modify the vector database as much. Apologies that the previous configurations and comments may have given the misleading conception that the vector db is configurable within the middleware services. I've since removed these. If you'd like to swap out weaviate for qdrant nevertheless, consider starting the services directly with something like `docker compose -f docker/docker-compose.middleware.yaml -f docker/docker-compose.yaml up -d db redis sandbox ssrf_proxy qdrant` Hope this helps!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 👻 feat:rag
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#4349
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?