Replies: 1 comment
-
|
Hi @r65068! I'm Dosu and I’m helping the dify team. The error happens because your environment (often a container or restricted filesystem) blocks Python from creating symlinks during virtual environment setup, which is required by Python 3.12. This is a common issue in Docker or when volumes are migrated with zip (which loses symlinks) instead of tar. You have a few options:
If you need more targeted help, sharing your OS, container runtime, and filesystem details can help pinpoint the restriction. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Self Checks
Content
2025/12/05 18:28:23 full_duplex.go:27: [INFO]new plugin logged in: langgenius/siliconflow:0.0.36
2025/12/05 18:28:23 full_duplex.go:59: [INFO]init environment for plugin langgenius/siliconflow:0.0.36
2025/12/05 18:28:24 full_duplex.go:65: [ERROR]init environment failed: failed to create virtual environment: exit status 2, output: Using CPython 3.12.3 interpreter at: /usr/bin/python3.12
Creating virtual environment at: .venv
error: Failed to create virtual environment
Caused by: failed to symlink file from /usr/bin/python3.12 to /app/storage/cwd/langgenius/siliconflow-0.0.36@9ce3ad7184c8858a8a7c3215ad8028dbbdb931966dd9da350c7cc1d12009beac/.venv/bin/python: Operation not permitted (os error 1)
, retrying
Beta Was this translation helpful? Give feedback.
All reactions