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

Forgot to expose Milvus standalone port in yaml #5215

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

Originally created by @winsonwhe on GitHub (Aug 26, 2024).

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

Dify version

0.7.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Follow the steps of Deploy with Docker Compose to setup Dify and Milvus, in docker compose yaml and Milvus part, it is lack of expose Milvus require port, leading to fail to connect with Milvus.

✔️ Expected Behavior

Correct yaml should refer https://github.com/milvus-io/milvus/blob/master/deployments/docker/standalone/docker-compose.yml

  milvus-standalone:
    container_name: milvus-standalone
    image: milvusdb/milvus:v2.3.1
    profiles:
      - milvus
    command: [ "milvus", "run", "standalone" ]
    environment:
      ETCD_ENDPOINTS: ${ETCD_ENDPOINTS:-etcd:2379}
      MINIO_ADDRESS: ${MINIO_ADDRESS:-minio:9000}
      common.security.authorizationEnabled: ${MILVUS_AUTHORIZATION_ENABLED:-true}
    volumes:
      - ./volumes/milvus/milvus:/var/lib/milvus
    healthcheck:
      test: [ "CMD", "curl", "-f", "http://localhost:9091/healthz" ]
      interval: 30s
      start_period: 90s
      timeout: 20s
      retries: 3
    **ports:
      - "19530:19530"
      - "9091:9091"**
    depends_on:
      - "etcd"
      - "minio"
    networks:
      - milvus

❌ Actual Behavior

No response

Originally created by @winsonwhe on GitHub (Aug 26, 2024). Originally assigned to: @JohnJyong 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.7.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Follow the steps of [Deploy with Docker Compose](https://docs.dify.ai/getting-started/install-self-hosted/docker-compose) to setup Dify and **Milvus**, in docker compose yaml and Milvus part, it is lack of expose Milvus require port, leading to fail to connect with Milvus. ### ✔️ Expected Behavior Correct yaml should refer https://github.com/milvus-io/milvus/blob/master/deployments/docker/standalone/docker-compose.yml ``` milvus-standalone: container_name: milvus-standalone image: milvusdb/milvus:v2.3.1 profiles: - milvus command: [ "milvus", "run", "standalone" ] environment: ETCD_ENDPOINTS: ${ETCD_ENDPOINTS:-etcd:2379} MINIO_ADDRESS: ${MINIO_ADDRESS:-minio:9000} common.security.authorizationEnabled: ${MILVUS_AUTHORIZATION_ENABLED:-true} volumes: - ./volumes/milvus/milvus:/var/lib/milvus healthcheck: test: [ "CMD", "curl", "-f", "http://localhost:9091/healthz" ] interval: 30s start_period: 90s timeout: 20s retries: 3 **ports: - "19530:19530" - "9091:9091"** depends_on: - "etcd" - "minio" networks: - milvus ``` ### ❌ Actual Behavior _No response_
yindo added the 👻 feat:rag label 2026-02-21 18:09:54 -05:00
yindo closed this issue 2026-02-21 18:09:54 -05:00
yindo commented 2026-02-21 18:09:54 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 26, 2024):

Hello @winsonwhe! I'm here to assist you with any bugs or questions you have regarding Dify. I can help you solve issues, answer questions, and even guide you on how to become a contributor. Let me know how I can assist you!

To expose the required Milvus standalone ports in the Docker Compose YAML for your self-hosted Dify setup, you need to add the ports section under the milvus-standalone service. Here is the corrected configuration:

milvus-standalone:
  container_name: milvus-standalone
  image: milvusdb/milvus:v2.3.1
  profiles:
    - milvus
  command: [ "milvus", "run", "standalone" ]
  environment:
    ETCD_ENDPOINTS: ${ETCD_ENDPOINTS:-etcd:2379}
    MINIO_ADDRESS: ${MINIO_ADDRESS:-minio:9000}
    common.security.authorizationEnabled: ${MILVUS_AUTHORIZATION_ENABLED:-true}
  volumes:
    - ./volumes/milvus/milvus:/var/lib/milvus
  healthcheck:
    test: [ "CMD", "curl", "-f", "http://localhost:9091/healthz" ]
    interval: 30s
    start_period: 90s
    timeout: 20s
    retries: 3
  ports:
    - "19530:19530"  # Milvus gRPC port
    - "9091:9091"    # Milvus HTTP port
  depends_on:
    - "etcd"
    - "minio"
  networks:
    - milvus

This configuration ensures that the Milvus gRPC port (19530) and the Milvus HTTP port (9091) are exposed to the host machine, allowing proper connectivity [1][2][3].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 26, 2024): <!-- Greeting --> Hello @winsonwhe! I'm here to assist you with any bugs or questions you have regarding Dify. I can help you solve issues, answer questions, and even guide you on how to become a contributor. Let me know how I can assist you! <!-- Answer --> To expose the required Milvus standalone ports in the Docker Compose YAML for your self-hosted Dify setup, you need to add the `ports` section under the `milvus-standalone` service. Here is the corrected configuration: ```yaml milvus-standalone: container_name: milvus-standalone image: milvusdb/milvus:v2.3.1 profiles: - milvus command: [ "milvus", "run", "standalone" ] environment: ETCD_ENDPOINTS: ${ETCD_ENDPOINTS:-etcd:2379} MINIO_ADDRESS: ${MINIO_ADDRESS:-minio:9000} common.security.authorizationEnabled: ${MILVUS_AUTHORIZATION_ENABLED:-true} volumes: - ./volumes/milvus/milvus:/var/lib/milvus healthcheck: test: [ "CMD", "curl", "-f", "http://localhost:9091/healthz" ] interval: 30s start_period: 90s timeout: 20s retries: 3 ports: - "19530:19530" # Milvus gRPC port - "9091:9091" # Milvus HTTP port depends_on: - "etcd" - "minio" networks: - milvus ``` This configuration ensures that the Milvus gRPC port (19530) and the Milvus HTTP port (9091) are exposed to the host machine, allowing proper connectivity <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/.github/workflows/expose_service_ports.sh)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/docker-legacy/docker-compose.milvus.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:09:55 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 26, 2024):

Please feel free to open a pr for this

@crazywoola commented on GitHub (Aug 26, 2024): Please feel free to open a pr for this
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#5215
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?