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

Docker update caused loss of previous member and application data!!! #781

New Issue
Closed
opened 2026-02-21 17:28:24 -05:00 by yindo · 9 comments
yindo commented 2026-02-21 17:28:24 -05:00
Owner
Copy Link
Copy Source

Originally created by @mozeqiu123 on GitHub (Dec 5, 2023).

Originally assigned to: @crazywoola on GitHub.

Dify version

0.3.30

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

I modified some front-end code and prepared to start, executed Docker Compose Up, which caused Docker updates, and then my application creation data was lost, along with some added members

✔️ Expected Behavior

Only update the front-end part

❌ Actual Behavior

Docker update caused data loss

Originally created by @mozeqiu123 on GitHub (Dec 5, 2023). Originally assigned to: @crazywoola on GitHub. ### Dify version 0.3.30 ### Cloud or Self Hosted Self Hosted (Docker), Self Hosted (Source) ### Steps to reproduce I modified some front-end code and prepared to start, executed Docker Compose Up, which caused Docker updates, and then my application creation data was lost, along with some added members ### ✔️ Expected Behavior Only update the front-end part ### ❌ Actual Behavior Docker update caused data loss
yindo added the 🐞 bug label 2026-02-21 17:28:24 -05:00
yindo closed this issue 2026-02-21 17:28:24 -05:00
yindo commented 2026-02-21 17:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 6, 2023):

Because you seems to use different ways to start the application which will cause the data will mismatch.
If you modify the source code, you should use the source code way to start your application again instead of using the docker.

@crazywoola commented on GitHub (Dec 6, 2023): Because you seems to use different ways to start the application which will cause the data will mismatch. If you modify the source code, you should use the source code way to start your application again instead of using the docker.
yindo commented 2026-02-21 17:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@mozeqiu123 commented on GitHub (Dec 6, 2023):

Because you seems to use different ways to start the application which will cause the data will mismatch. If you modify the source code, you should use the source code way to start your application again instead of using the docker.

😭

@mozeqiu123 commented on GitHub (Dec 6, 2023): > Because you seems to use different ways to start the application which will cause the data will mismatch. If you modify the source code, you should use the source code way to start your application again instead of using the docker. 😭
yindo commented 2026-02-21 17:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@mozeqiu123 commented on GitHub (Dec 6, 2023):

Because you seems to use different ways to start the application which will cause the data will mismatch. If you modify the source code, you should use the source code way to start your application again instead of using the docker.

So there's no way to restore it, right?

@mozeqiu123 commented on GitHub (Dec 6, 2023): > Because you seems to use different ways to start the application which will cause the data will mismatch. If you modify the source code, you should use the source code way to start your application again instead of using the docker. So there's no way to restore it, right?
yindo commented 2026-02-21 17:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 6, 2023):

I am not sure how you start the application, which db you want to restore as well.
If you are using the docker compose the data won't be removed unless you manually delete the folders under the docker/.

@crazywoola commented on GitHub (Dec 6, 2023): I am not sure how you start the application, which db you want to restore as well. If you are using the docker compose the data won't be removed unless you manually delete the folders under the docker/.
yindo commented 2026-02-21 17:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@mozeqiu123 commented on GitHub (Dec 6, 2023):

I am not sure how you start the application, which db you want to restore as well. If you are using the docker compose the data won't be removed unless you manually delete the folders under the docker/.

Let me provide a detailed description of my operational steps. I deployed the service using source code, and I am preparing to restart it. When I first started the database Docker, I used Docker Compose Up and then started Docker Update. I realized that I made a mistake, so I used Docker Compose - f Docker Compose. middleware. yaml up - d to start the service, start the API and web. When I logged in to Dify, I found that some of my previous applications were lost, and only a few were left, The volumes file in the Docker folder is still there and has not been modified. I would like to know how to proceed.😭😭😭

@mozeqiu123 commented on GitHub (Dec 6, 2023): > I am not sure how you start the application, which db you want to restore as well. If you are using the docker compose the data won't be removed unless you manually delete the folders under the docker/. Let me provide a detailed description of my operational steps. I deployed the service using source code, and I am preparing to restart it. When I first started the database Docker, I used Docker Compose Up and then started Docker Update. I realized that I made a mistake, so I used Docker Compose - f Docker Compose. middleware. yaml up - d to start the service, start the API and web. When I logged in to Dify, I found that some of my previous applications were lost, and only a few were left, The volumes file in the Docker folder is still there and has not been modified. I would like to know how to proceed.😭😭😭
yindo commented 2026-02-21 17:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 6, 2023):

In this case, I think the folder has been overrode by the compose. :(

@crazywoola commented on GitHub (Dec 6, 2023): In this case, I think the folder has been overrode by the compose. :(
yindo commented 2026-02-21 17:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@mozeqiu123 commented on GitHub (Dec 6, 2023):

In this case, I think the folder has been overrode by the compose. :(

Is there any way to restore it?
:(

@mozeqiu123 commented on GitHub (Dec 6, 2023): > In this case, I think the folder has been overrode by the compose. :( Is there any way to restore it? :(
yindo commented 2026-02-21 17:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@mozeqiu123 commented on GitHub (Dec 6, 2023):

In this case, I think the folder has been overrode by the compose. :(

What is the principle that causes overwriting? Will updating the Docker affect my local volumes file?

@mozeqiu123 commented on GitHub (Dec 6, 2023): > In this case, I think the folder has been overrode by the compose. :( What is the principle that causes overwriting? Will updating the Docker affect my local volumes file?
yindo commented 2026-02-21 17:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@mozeqiu123 commented on GitHub (Dec 6, 2023):

In this case, I think the folder has been overrode by the compose. :(

In theory, if the data is overwritten, there should be nothing, but if we trace back to the 14th (the time point when I pulled the code), there are still some residual data preserved.
image
If you need any information, please let me know

@mozeqiu123 commented on GitHub (Dec 6, 2023): > In this case, I think the folder has been overrode by the compose. :( In theory, if the data is overwritten, there should be nothing, but if we trace back to the 14th (the time point when I pulled the code), there are still some residual data preserved. ![image](https://github.com/langgenius/dify/assets/139750690/03d3d585-46c6-4ae7-8438-98d139d87691) If you need any information, please let me know
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#781
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?