Add persist-data boot probe to warn when data may not survive a restart#2396
Open
dsagal wants to merge 1 commit into
Open
Add persist-data boot probe to warn when data may not survive a restart#2396dsagal wants to merge 1 commit into
dsagal wants to merge 1 commit into
Conversation
Detects the common self-host mistake of running the Docker image without a volume mounted at /persist, where documents and the home DB live on the container's ephemeral filesystem and are lost on restart. We use a few heuristics: - We take GRIST_DATA_DIR set to the docker default is a sign of running in a container with ephemeral root. - We take GRIST_DATA_DIR as ephemeral if it's on the same mount as the ephemeral root, or if it's a RAM filesystem. - Using external document storage and Postgress count as durable. This check is surfaced as Quick Setup warning banner in the "Backups" page, and a boot probe check in the Admin Panel.
paulfitz
approved these changes
Jun 22, 2026
Member
|
@dsagal looks like some conflicts has accumulated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Detects the common self-host mistake of running the Docker image without a volume mounted at /persist, where documents and the home DB live on the container's ephemeral filesystem and are lost on restart.
Proposed solution
We use a few heuristics:
This check is surfaced as Quick Setup warning banner in the "Backups" page, and a boot probe check in the Admin Panel.
Related issues
Has this been tested?
This seems hard to test, it's about detecting what environment we are running in. Open to testing suggestions.
Screenshots / Screencasts