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

[PR #26618] upgrade docker compose milvus version to 2.6.0 to fix installation error #31494

New Issue
Closed
opened 2026-02-21 20:49:34 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:49:34 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/26618

State: closed
Merged: Yes

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

When try to install dify with milvus using docker-compose.yaml, milvus container quited with below error:

[2025/09/28 15:56:19.786 +00:00] [WARN] [proxy/listener_manager.go:49] ["Proxy fail to create external grpc listener"] [error="listen tcp :19530: bind: address already in use"] panic: listen tcp :19530: bind: address already in use

After checking again and again, there is no other process occupying the 19530 port. And then upgrade the milvus version from 2.5.15(default version) to 2.6.0(latest is 2.6.2), the error misses and milvus container runs well. Dify install works fine as well.

I looked the error on milvus github issues list, this issue is related to the error. Upgrade the milvus version can fix the error. In antoer way, the latest version for milvus is already 2.6.x, the verison in docker-compose.yaml is still 2.5.x, upgrade is a good choice.

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/26618 **State:** closed **Merged:** Yes --- > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 1. Ensure there is an associated issue and you have been assigned to it > 1. Use the correct syntax to link this PR: `Fixes #<issue number>`. ## Summary <!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> When try to install dify with milvus using [`docker-compose.yaml`](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml), milvus container quited with below error: ``` [2025/09/28 15:56:19.786 +00:00] [WARN] [proxy/listener_manager.go:49] ["Proxy fail to create external grpc listener"] [error="listen tcp :19530: bind: address already in use"] panic: listen tcp :19530: bind: address already in use ``` After checking again and again, there is no other process occupying the 19530 port. And then upgrade the milvus version from 2.5.15(default version) to 2.6.0([latest is 2.6.2](https://github.com/milvus-io/milvus/releases/tag/v2.6.2)), the error misses and milvus container runs well. Dify install works fine as well. I looked the error on [milvus github issues list](https://github.com/milvus-io/milvus/issues), [this issue](https://github.com/milvus-io/milvus/issues/30034) is related to the error. Upgrade the milvus version can fix the error. In antoer way, the latest version for milvus is already 2.6.x, the verison in `docker-compose.yaml` is still 2.5.x, upgrade is a good choice. ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:49:34 -05:00
yindo closed this issue 2026-02-21 20:49:34 -05:00
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 pull-request
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#31494
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?