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

A very serious bug occurred while installing the plugin #8894

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

Originally created by @LZW-Andrewlu on GitHub (Mar 3, 2025).

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

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image
As shown in the figure: When installing a plug-in, a timeout failure is always displayed, resulting in a failure to install the plug-in.
Further discovery: site-packages in the .venv directory in the plugin installation directory are constantly deleted and rebuilt, and files are constantly being written. Severely damaged disk life. Please fix it as soon as possible.

========================================================================

✔️ Expected Behavior

  1. Set a longer timeout when installing the plugin.
  2. After the installation fails, the downloaded dependency cache should not be deleted.
  3. Each retry should detect the installed dependencies and do not have to be re-installed.
  4. Reduce the frequency of disk writes and protect the life of the disk.

❌ Actual Behavior

No response

Originally created by @LZW-Andrewlu on GitHub (Mar 3, 2025). ### 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 1.0.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/0b8f6686-c204-4bec-81b9-7298e0b3378a) As shown in the figure: When installing a plug-in, a timeout failure is always displayed, resulting in a failure to install the plug-in. Further discovery: site-packages in the .venv directory in the plugin installation directory are constantly deleted and rebuilt, and files are constantly being written. Severely damaged disk life. Please fix it as soon as possible. ======================================================================== ### ✔️ Expected Behavior 1. Set a longer timeout when installing the plugin. 2. After the installation fails, the downloaded dependency cache should not be deleted. 3. Each retry should detect the installed dependencies and do not have to be re-installed. 4. Reduce the frequency of disk writes and protect the life of the disk. ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:28:28 -05:00
yindo closed this issue 2026-02-21 18:28:28 -05:00
yindo commented 2026-02-21 18:28:29 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

@LZW-Andrewlu Hello there! I'm here to help you with bug fixes, questions, and becoming a contributor. I'll assist you while we wait for a human maintainer.

To address the issues you're experiencing with the langgenius/ollama:0.0.3 plugin installation, you can try the following solutions:

  1. Increase Timeout: Modify your docker-compose.yaml file to increase the timeout for the plugin installation. Add the following environment variable under the plugin_daemon service:

    plugin_daemon:
  environment:
    PYTHON_ENV_INIT_TIMEOUT: 320

  2. Reduce Disk Writes: If you're using Windows, consider moving the dify/docker directory to the WSL filesystem instead of keeping it on Windows NTFS. This can help reduce disk writes.

  3. Specify Working Path: Add this environment variable to your .env file to specify a working path:

    PLUGIN_WORKING_PATH=/app/cwd

  4. Check Network Connection: Ensure your network connection is stable. If you're using Clash as your proxy, enable global TUN mode, as this has been known to solve installation timeout issues [1].

These steps should help mitigate the timeout and excessive disk write issues you're encountering.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 3, 2025): <!-- Greeting --> @LZW-Andrewlu Hello there! I'm here to help you with bug fixes, questions, and becoming a contributor. I'll assist you while we wait for a human maintainer. <!-- Answer --> To address the issues you're experiencing with the `langgenius/ollama:0.0.3` plugin installation, you can try the following solutions: 1. **Increase Timeout**: Modify your `docker-compose.yaml` file to increase the timeout for the plugin installation. Add the following environment variable under the `plugin_daemon` service: ```yaml plugin_daemon: environment: PYTHON_ENV_INIT_TIMEOUT: 320 ``` 2. **Reduce Disk Writes**: If you're using Windows, consider moving the `dify/docker` directory to the WSL filesystem instead of keeping it on Windows NTFS. This can help reduce disk writes. 3. **Specify Working Path**: Add this environment variable to your `.env` file to specify a working path: ``` PLUGIN_WORKING_PATH=/app/cwd ``` 4. **Check Network Connection**: Ensure your network connection is stable. If you're using Clash as your proxy, enable global TUN mode, as this has been known to solve installation timeout issues <sup>[[1]](https://github.com/langgenius/dify/issues/14664)</sup>. These steps should help mitigate the timeout and excessive disk write issues you're encountering. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/5dda87b0-d88d-48be-9711-4b0059ed9c43?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/5dda87b0-d88d-48be-9711-4b0059ed9c43?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/5dda87b0-d88d-48be-9711-4b0059ed9c43?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/5dda87b0-d88d-48be-9711-4b0059ed9c43?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5dda87b0-d88d-48be-9711-4b0059ed9c43?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/5dda87b0-d88d-48be-9711-4b0059ed9c43?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5dda87b0-d88d-48be-9711-4b0059ed9c43?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:29 -05:00
Author
Owner
Copy Link
Copy Source

@Araile commented on GitHub (Mar 3, 2025):

use 0.15.3 version can install ollama

@Araile commented on GitHub (Mar 3, 2025): use 0.15.3 version can install ollama
yindo commented 2026-02-21 18:28:29 -05:00
Author
Owner
Copy Link
Copy Source

@HuChundong commented on GitHub (Mar 3, 2025):

omg，you remind me. i should stop dify container right now~

@HuChundong commented on GitHub (Mar 3, 2025): omg，you remind me. i should stop dify container right now~
yindo commented 2026-02-21 18:28:29 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 5, 2025):

We fixed in https://github.com/langgenius/dify-plugin-daemon/pull/59

  plugin_daemon:
    image: langgenius/dify-plugin-daemon:e0672c3c1a6451437e8f4b63b260c8b0863c9c80-local
@crazywoola commented on GitHub (Mar 5, 2025): We fixed in https://github.com/langgenius/dify-plugin-daemon/pull/59 ``` plugin_daemon: image: langgenius/dify-plugin-daemon:e0672c3c1a6451437e8f4b63b260c8b0863c9c80-local ```
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 🐞 bug
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#8894
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?