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

[ERROR]init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds, retry in 30s #8831

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

Originally created by @bravet on GitHub (Mar 1, 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

2025/03/02 03:34:06 runtime_lifetime.go:76: [ERROR]init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds, retry in 30s

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @bravet on GitHub (Mar 1, 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 2025/03/02 03:34:06 runtime_lifetime.go:76: [ERROR]init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds, retry in 30s ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:27:57 -05:00
yindo commented 2026-02-21 18:27:57 -05:00
Author
Owner
Copy Link
Copy Source

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

Hey @bravet! 👋 I'm here to help you with any bugs, questions, or contributions you have for Dify. I'm a bot designed to assist you while you wait for a human maintainer. Let's tackle this together!

To resolve the error "init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds" when using Dify version 1.0.0 in a self-hosted Docker environment, you can try the following solutions:

  1. Downgrade Dify Version: This error is a known issue that has been addressed in version v0.15.3 of Dify. Downgrading to this version may resolve the problem.

  2. Extend the Timeout: Add the PYTHON_ENV_INIT_TIMEOUT environment variable to your docker-compose.yaml file under the plugin_daemon service configuration to extend the default 120-second timeout period:

    plugin_daemon:
  environment:
    PYTHON_ENV_INIT_TIMEOUT: 320

  3. Optimize File System Performance: If you are running Docker on Windows, consider moving the entire 'dify/docker' directory to the WSL filesystem instead of keeping it on Windows NTFS. This can help avoid performance degradation that occurs when binding NTFS folders as Docker volumes, which may cause the installation to exceed the timeout limit.

  4. Set Plugin Working Path: Alternatively, add the following environment variable to your .env file:

    PLUGIN_WORKING_PATH=/app/cwd

These solutions should help prevent the error during plugin installation by addressing both timeout and file system performance issues [1][2][3].

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 1, 2025): <!-- Greeting --> Hey @bravet! 👋 I'm here to help you with any bugs, questions, or contributions you have for Dify. I'm a bot designed to assist you while you wait for a human maintainer. Let's tackle this together! <!-- Answer --> To resolve the error "init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds" when using Dify version 1.0.0 in a self-hosted Docker environment, you can try the following solutions: 1. **Downgrade Dify Version**: This error is a known issue that has been addressed in version v0.15.3 of Dify. Downgrading to this version may resolve the problem. 2. **Extend the Timeout**: Add the `PYTHON_ENV_INIT_TIMEOUT` environment variable to your `docker-compose.yaml` file under the `plugin_daemon` service configuration to extend the default 120-second timeout period: ```yaml plugin_daemon: environment: PYTHON_ENV_INIT_TIMEOUT: 320 ``` 3. **Optimize File System Performance**: If you are running Docker on Windows, consider moving the entire 'dify/docker' directory to the WSL filesystem instead of keeping it on Windows NTFS. This can help avoid performance degradation that occurs when binding NTFS folders as Docker volumes, which may cause the installation to exceed the timeout limit. 4. **Set Plugin Working Path**: Alternatively, add the following environment variable to your `.env` file: ``` PLUGIN_WORKING_PATH=/app/cwd ``` These solutions should help prevent the error during plugin installation by addressing both timeout and file system performance issues <sup>[[1]](https://github.com/langgenius/dify/issues/14617)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/12635)</sup><sup>[[3]](https://github.com/langgenius/dify/issues/14241)</sup>. <!-- 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/b989969d-931d-4fc6-99e1-d170efd86601?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b989969d-931d-4fc6-99e1-d170efd86601?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b989969d-931d-4fc6-99e1-d170efd86601?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b989969d-931d-4fc6-99e1-d170efd86601?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b989969d-931d-4fc6-99e1-d170efd86601?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b989969d-931d-4fc6-99e1-d170efd86601?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b989969d-931d-4fc6-99e1-d170efd86601?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:57 -05:00
Author
Owner
Copy Link
Copy Source

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

Duplicated https://github.com/langgenius/dify/issues/14617

@crazywoola commented on GitHub (Mar 1, 2025): Duplicated https://github.com/langgenius/dify/issues/14617
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
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#8831
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?