Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Other]: MySQL data loss after Docker deployment restart #1461

Closed
whevether opened this issue Nov 22, 2023 · 6 comments
Closed

[Other]: MySQL data loss after Docker deployment restart #1461

whevether opened this issue Nov 22, 2023 · 6 comments
Labels
other Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@whevether
Copy link

What would you like to share?

MySQL data loss after Docker deployment restart, The data I want to add can be persisted, such as adding user data without loss

Additional information

No response
@whevether whevether added the other Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 22, 2023
@kubbot
Copy link
Contributor

kubbot commented Nov 22, 2023

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

@cubxxw
Copy link
Contributor

cubxxw commented Nov 22, 2023

Could you please confirm if the DATA_DIR directory in the .env file is set up correctly? The data directory should be located under the components/ directory in DATA_DIR.

@kubbot
Copy link
Contributor

kubbot commented Jan 21, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@cubxxw
Copy link
Contributor

cubxxw commented Jan 21, 2024

Has the issue been resolved at this point in time?

@kubbot
Copy link
Contributor

kubbot commented Mar 22, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot
Copy link
Contributor

kubbot commented Mar 31, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
other Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@whevether @cubxxw @kubbot