Repository navigation
Set 120s stop grace period for Halo app - #10605
Merged
wanghe-fit2cloud merged 1 commit intoNov 19, 2026
Merged
Conversation
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
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.
Background
Halo's graceful shutdown can take longer than Docker's default 10-second stop timeout, especially on instances with many plugins. When the timeout expires, the container is killed before Halo finishes stopping plugins and saving index snapshots, so the next startup cannot reuse the snapshot and may leave plugin resources in an inconsistent state.
This is the same issue addressed in the official deployment documentation (halo-dev/docs#649), but the 1Panel app package is missing the equivalent setting.
Changes
stop_grace_period: 120sto the Halo service inapps/halo/2.27.3/docker-compose.yml.Validation
apps/halo/2.27.3/docker-compose.ymlparses as valid YAML.