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

An error occurred when installing the offline plug-in #11838

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

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

dify_plugin

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

/app/storage/cwd/langgenius/openai_api_compatible-0.0.7@f20c7275bbcf055ec5d170dd5128e341986e2dcba5266d08fd080d4bdf2288f6/.venv/bin/python: error while loading shared libraries: libpython3.10.so.1.0: cannot open shared object file: No such file or directory
1.离线安装时将联网的机器下载好插件
2.将数数据库数据打包
3.将插件目录打包
4.放入离线服务器后运行报错

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @shines18523 on GitHub (Mar 19, 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 dify_plugin ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce /app/storage/cwd/langgenius/openai_api_compatible-0.0.7@f20c7275bbcf055ec5d170dd5128e341986e2dcba5266d08fd080d4bdf2288f6/.venv/bin/python: error while loading shared libraries: libpython3.10.so.1.0: cannot open shared object file: No such file or directory 1.离线安装时将联网的机器下载好插件 2.将数数据库数据打包 3.将插件目录打包 4.放入离线服务器后运行报错 ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:04:19 -05:00
yindo closed this issue 2026-02-21 19:04:19 -05:00
yindo commented 2026-02-21 19:04:19 -05:00
Author
Owner
Copy Link
Copy Source

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

Hello @shines18523! 👋 I'm here to help you with any bugs, questions, or contributions you may have while waiting for a human maintainer. Let's squash those bugs together!

I found a relevant discussion regarding issues with offline plugin installation in Dify. The known issue is that the installation process can fail due to missing dependencies when the environment cannot access the internet. One solution is to add your internal PIP mirror URL to the docker-compose.yaml file using the PIP_MIRROR_URL environment variable, allowing the plugin installer to fetch Python dependencies from your internal package repository [1].

Additionally, there are workarounds for handling plugin dependencies in offline installations:

  1. Downgrade to Dify version 0.15.3, which is confirmed to work in offline environments.
  2. For version 1.0.0, create a new plugin container image with all dependencies pre-installed while connected to the internet, then use docker commit to save the container as an image. Export and transfer the image to the offline environment, load it on the offline server, and use this pre-built image in your docker-compose configuration [2].

You can also use the PIP_EXTRA_ARGS parameter to specify local package directories for offline installation, which allows you to install dependencies from local directories without needing to set up a pypiserver [3].

For resolving shared library issues like the one you're encountering (libpython3.10.so.1.0: cannot open shared object file), ensure that the necessary shared libraries are available in your environment. You might need to configure the python_lib_path in config.yaml to include paths to these libraries [4].

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 19, 2025): <!-- Greeting --> Hello @shines18523! 👋 I'm here to help you with any bugs, questions, or contributions you may have while waiting for a human maintainer. Let's squash those bugs together! <!-- Answer --> I found a relevant discussion regarding issues with offline plugin installation in Dify. The known issue is that the installation process can fail due to missing dependencies when the environment cannot access the internet. One solution is to add your internal PIP mirror URL to the `docker-compose.yaml` file using the `PIP_MIRROR_URL` environment variable, allowing the plugin installer to fetch Python dependencies from your internal package repository <sup>[[1]](https://github.com/langgenius/dify/issues/15885)</sup>. Additionally, there are workarounds for handling plugin dependencies in offline installations: 1. Downgrade to Dify version 0.15.3, which is confirmed to work in offline environments. 2. For version 1.0.0, create a new plugin container image with all dependencies pre-installed while connected to the internet, then use `docker commit` to save the container as an image. Export and transfer the image to the offline environment, load it on the offline server, and use this pre-built image in your docker-compose configuration <sup>[[2]](https://github.com/langgenius/dify/issues/15627)</sup>. You can also use the `PIP_EXTRA_ARGS` parameter to specify local package directories for offline installation, which allows you to install dependencies from local directories without needing to set up a pypiserver <sup>[[3]](https://github.com/langgenius/dify/issues/15776)</sup>. For resolving shared library issues like the one you're encountering (`libpython3.10.so.1.0: cannot open shared object file`), ensure that the necessary shared libraries are available in your environment. You might need to configure the `python_lib_path` in `config.yaml` to include paths to these libraries <sup>[[4]](https://github.com/langgenius/dify/issues/11873)</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/2cb739f9-82ec-4731-8eba-ca76aaf92fde?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/2cb739f9-82ec-4731-8eba-ca76aaf92fde?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/2cb739f9-82ec-4731-8eba-ca76aaf92fde?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/2cb739f9-82ec-4731-8eba-ca76aaf92fde?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2cb739f9-82ec-4731-8eba-ca76aaf92fde?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/2cb739f9-82ec-4731-8eba-ca76aaf92fde?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2cb739f9-82ec-4731-8eba-ca76aaf92fde?feedback_type=other)</sup>
yindo commented 2026-02-21 19:04:19 -05:00
Author
Owner
Copy Link
Copy Source

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

You can try this repo https://github.com/junjiem/dify-plugin-repackaging

From the steps you provided, it's not an expected behavior. Please make sure the steps should be written in English.

@crazywoola commented on GitHub (Mar 19, 2025): You can try this repo https://github.com/junjiem/dify-plugin-repackaging From the steps you provided, it's not an expected behavior. Please make sure the steps should be written in English.
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#11838
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?