本地部署1.3.1版本,源码启动时发现问题 #15

Closed
opened 2026-02-16 05:18:52 -05:00 by yindo · 1 comment
Owner

Originally created by @SunYan-666 on GitHub (May 12, 2025).

问题描述

部署后,登录时,提示redis的版本不够高,需要7.4及以上的版本。修改配置(包括docker和api)之后,在api下执行uv sync 提示redis版本不能高于6.0
No solution found when resolving dependencies for split (python_full_version >= '3.12.4' and python_full_version < '3.13' and platform_python_implementation != 'PyPy' and sys_platform == 'linux'):Because only redis[hiredis]<=6.0.0 is available and your project depends on redis[hiredis]>=7.4,<8.dev0, we can conclude that your project's requirements are unsatisfiable.
hint: redis was requested with a pre-release marker (e.g., redis>=7.4,<8.dev0), but pre-releases weren't enabled (try: --prerelease=allow)

页面链接

https://github.com/langgenius/dify-docs-mintlify/blob/main/zh-hans/getting-started/install-self-hosted/local-source-code.mdx

建议修改

Originally created by @SunYan-666 on GitHub (May 12, 2025). ## 问题描述 <!-- 请简要描述您发现的问题 --> 部署后,登录时,提示redis的版本不够高,需要7.4及以上的版本。修改配置(包括docker和api)之后,在api下执行uv sync 提示redis版本不能高于6.0 No solution found when resolving dependencies for split (python_full_version >= '3.12.4' and python_full_version < '3.13' and platform_python_implementation != 'PyPy' and sys_platform == 'linux'):Because only redis[hiredis]<=6.0.0 is available and your project depends on redis[hiredis]>=7.4,<8.dev0, we can conclude that your project's requirements are unsatisfiable. hint: `redis` was requested with a pre-release marker (e.g., redis>=7.4,<8.dev0), but pre-releases weren't enabled (try: `--prerelease=allow`) ## 页面链接 https://github.com/langgenius/dify-docs-mintlify/blob/main/zh-hans/getting-started/install-self-hosted/local-source-code.mdx ## 建议修改 <!-- 如果有具体的修改建议,请在此说明 --> <!-- 感谢您对文档质量的关注! -->
yindo closed this issue 2026-02-16 05:18:52 -05:00
Author
Owner

@QuantumGhost commented on GitHub (May 21, 2025):

Hi @SunYan-666,

Thank you for taking the time to report this issue. This specific problem was addressed in langgenius/dify#19524 and has been resolved as part of the v1.4.0 release.

Could you please try upgrading Dify to version 1.4.0 and let us know if the issue persists?

Looking forward to your feedback!

@QuantumGhost commented on GitHub (May 21, 2025): Hi @SunYan-666, Thank you for taking the time to report this issue. This specific problem was addressed in langgenius/dify#19524 and has been resolved as part of the v1.4.0 release. Could you please try upgrading Dify to version 1.4.0 and let us know if the issue persists? Looking forward to your feedback!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-docs#15