Use --wait in the default setup command
#129
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
Tasssadar
approved these changes
Nov 12, 2025
Member
Tasssadar
left a comment
Tasssadar
left a comment
There was a problem hiding this comment.
Added 4 years ago https://github.com/docker/compose/releases/tag/v2.1.1
So I think it should be fine, thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
--waitis the better-dthese days.I was slightly confused about the docs suggesting to implement a custom
wait_until_responsivewhen there was a native waiting mechanism. Judging by this old discussion - I could guess that--waitdid not yet exist back then.