dockercompose: add wait_for_healthy optional argument to docker_compose (#2239) #6329
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 is a tentative solution for #2239
I imagine the ideal case would be to do something fancy in
internal/dockercompose/state.go
to check the status, but as far as I could tell, the library that is being used under the hood there doesn't support checking whether a container is healthy.Simply adding
--wait
to the docker compose up command seems to make my health checks work properly. This might have side effects, but in the project that I've been submitting all these PRs for, it makes the race condition problems go away and I don't see any issues.Tests seem to pass locally.