langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-27 21:10:04 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Inconsitency between PLUGIN_WORKING_PATH and mount path for persistent volume #10914

New Issue
Closed
opened 2026-02-21 18:52:41 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:52:41 -05:00
Owner
Copy Link
Copy Source

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

v1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

https://github.com/langgenius/dify/blob/e796937d0233578abcd92dd2779a220a7b90e099/docker/docker-compose.yaml#L570-L578
The PLUGIN_WORKING_PATH suggest /app/storage/cwd while the persistent volume were mounted as path /app/storage. So what else were to be persisted in /app/storage besides /app/storage/cwd? Is /app/storage hardcoded in pluginDaemon for data persistence.

✔️ Expected Behavior

Path for data persistent should be configurable or at least explicitly documented.

❌ Actual Behavior

https://github.com/BorisPolonsky/dify-helm/pull/148
Some user claims that persistency doesn't work as expected when persistent volume were mount as /app/storage/cwd

Originally created by @BorisPolonsky on GitHub (Mar 13, 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 v1.0.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce https://github.com/langgenius/dify/blob/e796937d0233578abcd92dd2779a220a7b90e099/docker/docker-compose.yaml#L570-L578 The `PLUGIN_WORKING_PATH` suggest `/app/storage/cwd` while the persistent volume were mounted as path `/app/storage`. So what else were to be persisted in `/app/storage` besides `/app/storage/cwd`? Is `/app/storage` hardcoded in `pluginDaemon` for data persistence. ### ✔️ Expected Behavior Path for data persistent should be configurable or at least explicitly documented. ### ❌ Actual Behavior https://github.com/BorisPolonsky/dify-helm/pull/148 Some user claims that persistency doesn't work as expected when persistent volume were mount as `/app/storage/cwd`
yindo added the 📚 documentation label 2026-02-21 18:52:41 -05:00
yindo closed this issue 2026-02-21 18:52:41 -05:00
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 📚 documentation
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#10914
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?