feat!: add container startup timeout with default of 1 minute #643
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.
Closes #247
RunnableImage::with_startup_timeout
Note: breaking change because of default timeout
For now, ENV variable to configure global timeout isn't introduced. First of all, that's quote similar to other languages, (e.g Go, Java)
Another question is which one should take precedence: ENV over
with_startup_timeout
or vice versa?We can extend it later in compatible way, so not that important at the moment.