[mock_uss] Increase start_period for healthchecks and add timeout for mock_uss healthchecks.#1392
Merged
mickmis merged 1 commit intointeruss:mainfrom Mar 11, 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
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.
This should fix #1390.
It seems that if a service is marked as unhealthy, docker compose will stop immediately to wait ( docker/compose#10209 )
The change on the wait period had no impact in that case.
I switched to 30s in the compose-file, that should give more time for the containers to start (instead of default value of 5s).
I also fixed the healthcheck command used to have a short timeout, should the issue being that a curl is stuck waiting on tcp timeout, that could also explain the issue.