Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
5 tasks done
poechia opened this issue Mar 8, 2025 · 2 comments
Labels
🐞 bug Something isn't working cloud When the version is cloud and it is a bug report

Comments

@poechia
Copy link

poechia commented Mar 8, 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

Dify1.0 plugin daemon

Cloud or Self Hosted

Cloud

Steps to reproduce

Image
Image

✔️ Expected Behavior

Link to XInference Custom Models

❌ Actual Behavior

The Xinference plugin cannot be installed, so custom models cannot be linked

@dosubot dosubot bot added cloud When the version is cloud and it is a bug report 🐞 bug Something isn't working labels Mar 8, 2025
Copy link

dosubot bot commented Mar 8, 2025

Hey @poechia! I'm here to help you out with any bugs, questions, or contributions you might have. Let's squash those bugs 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 installing the Xinference plugin in a Docker container, you can try the following solutions:

  1. Extend the Timeout Period: Increase the timeout period for the Python environment initialization by adding the PYTHON_ENV_INIT_TIMEOUT environment variable to your docker-compose.yaml file under the plugin_daemon service configuration. Set it to a higher value, such as 320 seconds:

    plugin_daemon:
      environment:
        PYTHON_ENV_INIT_TIMEOUT: 320
  2. Optimize File System Usage on Windows: If you are using Docker on Windows, consider moving the dify/docker directory to the WSL filesystem instead of using Windows NTFS to improve performance.

  3. Set Plugin Working Path: Add the following environment variable to your .env file to specify the plugin working path:

    PLUGIN_WORKING_PATH=/app/cwd
    

Additionally, if you're using an internal network, consider setting the PIP_MIRROR_URL environment variable in plugin_daemon to use a mirror URL (e.g., https://pypi.tuna.tsinghua.edu.cn/simple) to potentially improve installation speed [1].

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

@crazywoola
Copy link
Member

crazywoola commented Mar 9, 2025

Duplicated See this langgenius/dify-plugin-daemon#59

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working cloud When the version is cloud and it is a bug report
Projects
None yet
Development

No branches or pull requests

2 participants