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

docker compose deploy, no Weaviate container #4637

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

Originally created by @npe2023 on GitHub (Jul 16, 2024).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

local docker compose deploy, not found Weaviate container, what went wrong?

✔️ Expected Behavior

should have Weaviate container

❌ Actual Behavior

image
Originally created by @npe2023 on GitHub (Jul 16, 2024). ### 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.14 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce local docker compose deploy, not found Weaviate container, what went wrong? ### ✔️ Expected Behavior should have Weaviate container ### ❌ Actual Behavior <img width="804" alt="image" src="https://github.com/user-attachments/assets/88f4dd6d-7773-4d6d-9b28-ec0db65299eb">
yindo added the 👻 feat:rag label 2026-02-21 18:07:20 -05:00
yindo closed this issue 2026-02-21 18:07:20 -05:00
yindo commented 2026-02-21 18:07:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 16, 2024):

Hello @npe2023! 👋 I'm here to help you with any bugs, questions, or contributions you have for the Dify project. If you need assistance, feel free to ask!

The Weaviate container might be missing because the docker-compose.middleware.yaml file includes commented-out sections for the Qdrant vector store. If you uncommented the Qdrant service, you need to comment out the Weaviate service. Ensure that the Weaviate service is not commented out in your docker-compose.middleware.yaml file.

# The Weaviate vector store.
weaviate:
  image: semitechnologies/weaviate:1.19.0
  restart: always
  volumes:
    # Mount the Weaviate data directory to the container.
    - ./volumes/weaviate:/var/lib/weaviate
  environment:
    # The Weaviate configurations
    # You can refer to the [Weaviate](https://weaviate.io/developers/weaviate/config-refs/env-vars) documentation for more information.
    QUERY_DEFAULTS_LIMIT: 25
    AUTHENTICATION_ANONYMOUS_ACCESS_ENABLED: 'false'
    PERSISTENCE_DATA_PATH: '/var/lib/weaviate'
    DEFAULT_VECTORIZER_MODULE: 'none'
    CLUSTER_HOSTNAME: 'node1'
    AUTHENTICATION_APIKEY_ENABLED: 'true'
    AUTHENTICATION_APIKEY_ALLOWED_KEYS: 'WVF5YThaHlkYwhGUSmCRgsX3tD5ngdN8pkih'
    AUTHENTICATION_APIKEY_USERS: 'hello@dify.ai'
    AUTHORIZATION_ADMINLIST_ENABLED: 'true'
    AUTHORIZATION_ADMINLIST_USERS: 'hello@dify.ai'
  # uncomment to expose weaviate port to host
  # ports:
  #  - "8080:8080"

Make sure the Qdrant service is commented out if you intend to use Weaviate:

# Qdrant vector store.
# (if used, you need to set VECTOR_STORE to qdrant in the api & worker service.)
# qdrant:
#   image: langgenius/qdrant:v1.7.3
#   restart: always
#   volumes:
#     - ./volumes/qdrant:/qdrant/storage
#   environment:
#     QDRANT_API_KEY: ${QDRANT_API_KEY:-difyai123456}
#   # uncomment to expose qdrant port to host
#   ports:
#     - "6333:6333"
#     - "6334:6334"

Additionally, ensure that the VECTOR_STORE environment variable is set to weaviate in your configuration:

# The type of vector store to use. Supported values are `weaviate`, `qdrant`, `milvus`, `relyt`, `pgvector`, `chroma`, 'opensearch', 'tidb_vector'.
VECTOR_STORE: weaviate
# The Weaviate endpoint URL. Only available when VECTOR_STORE is `weaviate`.
WEAVIATE_ENDPOINT: http://weaviate:8080
# The Weaviate API key.
WEAVIATE_API_KEY: WVF5YThaHlkYwhGUSmCRgsX3tD5ngdN8pkih

If you are still facing issues, ensure that you are not encountering any cross-domain or CORS errors, which can sometimes cause services to not start correctly. Check the docker-compose.yml file for correct domain name configurations and ensure that the CONSOLE_API_URL, CONSOLE_WEB_URL, SERVICE_API_URL, and APP_API_URL are set correctly to avoid cross-domain issues [1][2][3][4].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 16, 2024): <!-- Greeting --> Hello @npe2023! 👋 I'm here to help you with any bugs, questions, or contributions you have for the Dify project. If you need assistance, feel free to ask! <!-- Answer --> The Weaviate container might be missing because the `docker-compose.middleware.yaml` file includes commented-out sections for the Qdrant vector store. If you uncommented the Qdrant service, you need to comment out the Weaviate service. Ensure that the Weaviate service is not commented out in your `docker-compose.middleware.yaml` file. ```yaml # The Weaviate vector store. weaviate: image: semitechnologies/weaviate:1.19.0 restart: always volumes: # Mount the Weaviate data directory to the container. - ./volumes/weaviate:/var/lib/weaviate environment: # The Weaviate configurations # You can refer to the [Weaviate](https://weaviate.io/developers/weaviate/config-refs/env-vars) documentation for more information. QUERY_DEFAULTS_LIMIT: 25 AUTHENTICATION_ANONYMOUS_ACCESS_ENABLED: 'false' PERSISTENCE_DATA_PATH: '/var/lib/weaviate' DEFAULT_VECTORIZER_MODULE: 'none' CLUSTER_HOSTNAME: 'node1' AUTHENTICATION_APIKEY_ENABLED: 'true' AUTHENTICATION_APIKEY_ALLOWED_KEYS: 'WVF5YThaHlkYwhGUSmCRgsX3tD5ngdN8pkih' AUTHENTICATION_APIKEY_USERS: 'hello@dify.ai' AUTHORIZATION_ADMINLIST_ENABLED: 'true' AUTHORIZATION_ADMINLIST_USERS: 'hello@dify.ai' # uncomment to expose weaviate port to host # ports: # - "8080:8080" ``` Make sure the Qdrant service is commented out if you intend to use Weaviate: ```yaml # Qdrant vector store. # (if used, you need to set VECTOR_STORE to qdrant in the api & worker service.) # qdrant: # image: langgenius/qdrant:v1.7.3 # restart: always # volumes: # - ./volumes/qdrant:/qdrant/storage # environment: # QDRANT_API_KEY: ${QDRANT_API_KEY:-difyai123456} # # uncomment to expose qdrant port to host # ports: # - "6333:6333" # - "6334:6334" ``` Additionally, ensure that the `VECTOR_STORE` environment variable is set to `weaviate` in your configuration: ```yaml # The type of vector store to use. Supported values are `weaviate`, `qdrant`, `milvus`, `relyt`, `pgvector`, `chroma`, 'opensearch', 'tidb_vector'. VECTOR_STORE: weaviate # The Weaviate endpoint URL. Only available when VECTOR_STORE is `weaviate`. WEAVIATE_ENDPOINT: http://weaviate:8080 # The Weaviate API key. WEAVIATE_API_KEY: WVF5YThaHlkYwhGUSmCRgsX3tD5ngdN8pkih ``` If you are still facing issues, ensure that you are not encountering any cross-domain or CORS errors, which can sometimes cause services to not start correctly. Check the `docker-compose.yml` file for correct domain name configurations and ensure that the `CONSOLE_API_URL`, `CONSOLE_WEB_URL`, `SERVICE_API_URL`, and `APP_API_URL` are set correctly to avoid cross-domain issues <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker-legacy/docker-compose.middleware.yaml)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/docker-legacy/docker-compose.yaml)</sup><sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/install-faq.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:07:20 -05:00
Author
Owner
Copy Link
Copy Source

@npe2023 commented on GitHub (Jul 17, 2024):

fixed.

your document never mention to copy the .env.example file in the docker folder. please update the document when u have time.

thanks.

@npe2023 commented on GitHub (Jul 17, 2024): fixed. your document never mention to copy the `.env.example` file in the docker folder. please update the document when u have time. thanks.
yindo commented 2026-02-21 18:07:20 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 17, 2024):

@npe2023 Which doc are you referring to?

https://docs.dify.ai/v/zh-hans/getting-started/install-self-hosted/docker-compose
https://docs.dify.ai/getting-started/install-self-hosted/docker-compose

I have checked the docs site, it seems it's already written to cp .env.example .env

And the readme in this repo

image
@crazywoola commented on GitHub (Jul 17, 2024): @npe2023 Which doc are you referring to? https://docs.dify.ai/v/zh-hans/getting-started/install-self-hosted/docker-compose https://docs.dify.ai/getting-started/install-self-hosted/docker-compose I have checked the docs site, it seems it's already written to `cp .env.example .env` And the readme in this repo <img width="1027" alt="image" src="https://github.com/user-attachments/assets/bb74bb7c-4b0c-4756-8f44-56ddb44b7d13">
yindo commented 2026-02-21 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@npe2023 commented on GitHub (Jul 17, 2024):

https://docs.dify.ai/getting-started/install-self-hosted/local-source-code

this section doesn't mention

@npe2023 commented on GitHub (Jul 17, 2024): https://docs.dify.ai/getting-started/install-self-hosted/local-source-code this section doesn't mention
yindo commented 2026-02-21 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@npe2023 commented on GitHub (Jul 17, 2024):

@crazywoola one more thing , is there any GUI IDE to connect to weaviate, like any other database so i can view、query the data ?

@npe2023 commented on GitHub (Jul 17, 2024): @crazywoola one more thing , is there any GUI IDE to connect to weaviate, like any other database so i can view、query the data ?
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#4637
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?