[PANIC]failed to install python dependencies: exit status 1 #7748

Closed
opened 2026-02-21 18:22:10 -05:00 by yindo · 3 comments
Owner

Originally created by @Modas-Li on GitHub (Jan 16, 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

V0.15.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

sandbox-1     | 2025/01/16 05:12:53 setup.go:29: [INFO]initializing nodejs runner environment...
sandbox-1     | 2025/01/16 05:12:53 setup.go:85: [INFO]nodejs runner environment initialized
sandbox-1     | 2025/01/16 05:12:53 setup.go:33: [INFO]initializing python runner environment...
sandbox-1     | 2025/01/16 05:12:53 config.go:129: [INFO]network has been enabled
sandbox-1     | 2025/01/16 05:12:53 config.go:145: [INFO]using https proxy: http://ssrf_proxy:3128
sandbox-1     | 2025/01/16 05:12:53 config.go:154: [INFO]using http proxy: http://ssrf_proxy:3128
sandbox-1     | 2025/01/16 05:12:53 server.go:20: [INFO]config init success
sandbox-1     | 2025/01/16 05:12:53 server.go:26: [INFO]runner dependencies init success
sandbox-1     | 2025/01/16 05:12:53 cocrrent.go:31: [INFO]setting max requests to 50
sandbox-1     | 2025/01/16 05:12:53 cocrrent.go:13: [INFO]setting max workers to 4
sandbox-1     | 2025/01/16 05:12:53 server.go:47: [INFO]installing python dependencies...
sandbox-1     | 2025/01/16 05:12:54 setup.go:140: [INFO]Collecting pandas
sandbox-1     | 2025/01/16 05:12:54 setup.go:140: [INFO]  Using cached pandas-2.2.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (13.1 MB)
sandbox-1     | 2025/01/16 05:12:54 setup.go:140: [INFO]Collecting scikit-learn
sandbox-1     | 2025/01/16 05:12:54 setup.go:140: [INFO]  Using cached scikit_learn-1.6.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (13.5 MB)
sandbox-1     | 2025/01/16 05:12:54 setup.go:140: [INFO]Collecting xlrd
sandbox-1     | 2025/01/16 05:12:54 setup.go:140: [INFO]  Using cached xlrd-2.0.1-py2.py3-none-any.whl (96 kB)
sandbox-1     | 2025/01/16 05:12:55 setup.go:140: [INFO]Collecting xlwt
sandbox-1     | 2025/01/16 05:12:55 setup.go:140: [INFO]  Using cached xlwt-1.3.0-py2.py3-none-any.whl (99 kB)
sandbox-1     | 2025/01/16 05:12:55 setup.go:146: [ERROR]failed to wait for the command to complete
sandbox-1     | 2025/01/16 05:12:55 server.go:51: [PANIC]failed to install python dependencies: exit status 1
sandbox-1     | panic:
sandbox-1     |
sandbox-1     | goroutine 28 [running]:
sandbox-1     | github.com/langgenius/dify-sandbox/internal/utils/log.(*Log).Panic(...)
sandbox-1     |         /home/runner/work/dify-sandbox/dify-sandbox/internal/utils/log/core.go:55
sandbox-1     | github.com/langgenius/dify-sandbox/internal/utils/log.Panic({0x8ff40e?, 0x21?}, {0xc0005bbfc0?, 0x0?, 0x0?})
sandbox-1     |         /home/runner/work/dify-sandbox/dify-sandbox/internal/utils/log/core.go:209 +0x6f
sandbox-1     | github.com/langgenius/dify-sandbox/internal/server.initDependencies()
sandbox-1     |         /home/runner/work/dify-sandbox/dify-sandbox/internal/server/server.go:51 +0x86
sandbox-1     | created by github.com/langgenius/dify-sandbox/internal/server.Run
sandbox-1     |         /home/runner/work/dify-sandbox/dify-sandbox/internal/server/server.go:97 +0x25

python_path: /usr/local/bin/python3 changed to /data/anaconda3

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @Modas-Li on GitHub (Jan 16, 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 V0.15.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ``` sandbox-1 | 2025/01/16 05:12:53 setup.go:29: [INFO]initializing nodejs runner environment... sandbox-1 | 2025/01/16 05:12:53 setup.go:85: [INFO]nodejs runner environment initialized sandbox-1 | 2025/01/16 05:12:53 setup.go:33: [INFO]initializing python runner environment... sandbox-1 | 2025/01/16 05:12:53 config.go:129: [INFO]network has been enabled sandbox-1 | 2025/01/16 05:12:53 config.go:145: [INFO]using https proxy: http://ssrf_proxy:3128 sandbox-1 | 2025/01/16 05:12:53 config.go:154: [INFO]using http proxy: http://ssrf_proxy:3128 sandbox-1 | 2025/01/16 05:12:53 server.go:20: [INFO]config init success sandbox-1 | 2025/01/16 05:12:53 server.go:26: [INFO]runner dependencies init success sandbox-1 | 2025/01/16 05:12:53 cocrrent.go:31: [INFO]setting max requests to 50 sandbox-1 | 2025/01/16 05:12:53 cocrrent.go:13: [INFO]setting max workers to 4 sandbox-1 | 2025/01/16 05:12:53 server.go:47: [INFO]installing python dependencies... sandbox-1 | 2025/01/16 05:12:54 setup.go:140: [INFO]Collecting pandas sandbox-1 | 2025/01/16 05:12:54 setup.go:140: [INFO] Using cached pandas-2.2.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (13.1 MB) sandbox-1 | 2025/01/16 05:12:54 setup.go:140: [INFO]Collecting scikit-learn sandbox-1 | 2025/01/16 05:12:54 setup.go:140: [INFO] Using cached scikit_learn-1.6.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (13.5 MB) sandbox-1 | 2025/01/16 05:12:54 setup.go:140: [INFO]Collecting xlrd sandbox-1 | 2025/01/16 05:12:54 setup.go:140: [INFO] Using cached xlrd-2.0.1-py2.py3-none-any.whl (96 kB) sandbox-1 | 2025/01/16 05:12:55 setup.go:140: [INFO]Collecting xlwt sandbox-1 | 2025/01/16 05:12:55 setup.go:140: [INFO] Using cached xlwt-1.3.0-py2.py3-none-any.whl (99 kB) sandbox-1 | 2025/01/16 05:12:55 setup.go:146: [ERROR]failed to wait for the command to complete sandbox-1 | 2025/01/16 05:12:55 server.go:51: [PANIC]failed to install python dependencies: exit status 1 sandbox-1 | panic: sandbox-1 | sandbox-1 | goroutine 28 [running]: sandbox-1 | github.com/langgenius/dify-sandbox/internal/utils/log.(*Log).Panic(...) sandbox-1 | /home/runner/work/dify-sandbox/dify-sandbox/internal/utils/log/core.go:55 sandbox-1 | github.com/langgenius/dify-sandbox/internal/utils/log.Panic({0x8ff40e?, 0x21?}, {0xc0005bbfc0?, 0x0?, 0x0?}) sandbox-1 | /home/runner/work/dify-sandbox/dify-sandbox/internal/utils/log/core.go:209 +0x6f sandbox-1 | github.com/langgenius/dify-sandbox/internal/server.initDependencies() sandbox-1 | /home/runner/work/dify-sandbox/dify-sandbox/internal/server/server.go:51 +0x86 sandbox-1 | created by github.com/langgenius/dify-sandbox/internal/server.Run sandbox-1 | /home/runner/work/dify-sandbox/dify-sandbox/internal/server/server.go:97 +0x25 ``` python_path: /usr/local/bin/python3 changed to /data/anaconda3 ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:22:10 -05:00
yindo closed this issue 2026-02-21 18:22:10 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jan 16, 2025):

The error message "[PANIC]failed to install python dependencies: exit status 1" suggests that there was an issue during the installation of Python dependencies in your Dify setup. Here are a few steps you can take to troubleshoot and potentially resolve this issue:

  1. Check Proxy Settings: The logs indicate that an HTTP and HTTPS proxy is being used. Ensure that the proxy settings are correct and that the proxy server is accessible. Incorrect proxy settings can lead to network issues during dependency installation.

  2. Python Path Change: The log mentions a change in the Python path from /usr/local/bin/python3 to /data/anaconda3. Ensure that the new Python path is correctly set up and that it has all the necessary permissions and configurations to install packages.

  3. Dependency Conflicts: Check if there are any conflicts or issues with the specific versions of the dependencies being installed. You might want to try installing them manually in a separate environment to see if any specific package is causing the issue.

  4. Resource Limits: The logs mention setting max requests and workers. Ensure that your system has enough resources (CPU, memory) to handle the installation process, especially if it's running in a constrained environment like Docker.

  5. Docker Configuration: Since you are using a self-hosted Docker setup, verify that the Docker container has access to the internet and that there are no network restrictions preventing it from downloading the dependencies.

If these steps do not resolve the issue, you might want to look into the specific error logs generated during the installation process for more detailed information on what might be causing the failure.

To continue talking to Dosu, mention @dosu.


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

@dosubot[bot] commented on GitHub (Jan 16, 2025): <!-- Answer --> The error message "[PANIC]failed to install python dependencies: exit status 1" suggests that there was an issue during the installation of Python dependencies in your Dify setup. Here are a few steps you can take to troubleshoot and potentially resolve this issue: 1. **Check Proxy Settings**: The logs indicate that an HTTP and HTTPS proxy is being used. Ensure that the proxy settings are correct and that the proxy server is accessible. Incorrect proxy settings can lead to network issues during dependency installation. 2. **Python Path Change**: The log mentions a change in the Python path from `/usr/local/bin/python3` to `/data/anaconda3`. Ensure that the new Python path is correctly set up and that it has all the necessary permissions and configurations to install packages. 3. **Dependency Conflicts**: Check if there are any conflicts or issues with the specific versions of the dependencies being installed. You might want to try installing them manually in a separate environment to see if any specific package is causing the issue. 4. **Resource Limits**: The logs mention setting max requests and workers. Ensure that your system has enough resources (CPU, memory) to handle the installation process, especially if it's running in a constrained environment like Docker. 5. **Docker Configuration**: Since you are using a self-hosted Docker setup, verify that the Docker container has access to the internet and that there are no network restrictions preventing it from downloading the dependencies. If these steps do not resolve the issue, you might want to look into the specific error logs generated during the installation process for more detailed information on what might be causing the failure. <!-- 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/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=other)</sup>
Author
Owner

@Modas-Li commented on GitHub (Jan 16, 2025):

The error message "[PANIC]failed to install python dependencies: exit status 1" suggests that there was an issue during the installation of Python dependencies in your Dify setup. Here are a few steps you can take to troubleshoot and potentially resolve this issue:

  1. Check Proxy Settings: The logs indicate that an HTTP and HTTPS proxy is being used. Ensure that the proxy settings are correct and that the proxy server is accessible. Incorrect proxy settings can lead to network issues during dependency installation.
  2. Python Path Change: The log mentions a change in the Python path from /usr/local/bin/python3 to /data/anaconda3. Ensure that the new Python path is correctly set up and that it has all the necessary permissions and configurations to install packages.
  3. Dependency Conflicts: Check if there are any conflicts or issues with the specific versions of the dependencies being installed. You might want to try installing them manually in a separate environment to see if any specific package is causing the issue.
  4. Resource Limits: The logs mention setting max requests and workers. Ensure that your system has enough resources (CPU, memory) to handle the installation process, especially if it's running in a constrained environment like Docker.
  5. Docker Configuration: Since you are using a self-hosted Docker setup, verify that the Docker container has access to the internet and that there are no network restrictions preventing it from downloading the dependencies.

If these steps do not resolve the issue, you might want to look into the specific error logs generated during the installation process for more detailed information on what might be causing the failure.

To continue talking to Dosu, mention @dosu.

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

those dependencies are already downloaded and cached

@Modas-Li commented on GitHub (Jan 16, 2025): > The error message "[PANIC]failed to install python dependencies: exit status 1" suggests that there was an issue during the installation of Python dependencies in your Dify setup. Here are a few steps you can take to troubleshoot and potentially resolve this issue: > > 1. **Check Proxy Settings**: The logs indicate that an HTTP and HTTPS proxy is being used. Ensure that the proxy settings are correct and that the proxy server is accessible. Incorrect proxy settings can lead to network issues during dependency installation. > 2. **Python Path Change**: The log mentions a change in the Python path from `/usr/local/bin/python3` to `/data/anaconda3`. Ensure that the new Python path is correctly set up and that it has all the necessary permissions and configurations to install packages. > 3. **Dependency Conflicts**: Check if there are any conflicts or issues with the specific versions of the dependencies being installed. You might want to try installing them manually in a separate environment to see if any specific package is causing the issue. > 4. **Resource Limits**: The logs mention setting max requests and workers. Ensure that your system has enough resources (CPU, memory) to handle the installation process, especially if it's running in a constrained environment like Docker. > 5. **Docker Configuration**: Since you are using a self-hosted Docker setup, verify that the Docker container has access to the internet and that there are no network restrictions preventing it from downloading the dependencies. > > If these steps do not resolve the issue, you might want to look into the specific error logs generated during the installation process for more detailed information on what might be causing the failure. > > _To continue talking to [Dosu](https://dosu.dev), mention @dosu._ > > Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/f2c9bf94-11f5-4234-9061-668b7212b844?feedback_type=other) those dependencies are already downloaded and cached
Author
Owner

@crazywoola commented on GitHub (Jan 20, 2025):

Please open an issue here instead https://github.com/langgenius/dify-sandbox

@crazywoola commented on GitHub (Jan 20, 2025): Please open an issue here instead https://github.com/langgenius/dify-sandbox
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7748