fix(docker): increase health check start period to 90s#86
Merged
maartenbode merged 1 commit intomainfrom Mar 31, 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
1 participant
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.
Summary
The app container's entrypoint runs database migrations and cache warming before FrankenPHP starts, leaving the
/healthendpoint unreachable during initialization. With astart_periodof only 30s, slower environments exhaust the grace period and retries (~120s total), causing Docker to mark the container as unhealthy.Increases
start_periodfrom 30s to 90s in the Dockerfile and both Compose files, giving the entrypoint enough headroom for migrations and cache warming before health check failures start counting.Reported by a user running Docker where the app container consistently failed at ~127s with
container pricore-app is unhealthy.