fix(entrypoint): Delay on auto-install to avoid error before retry #2222
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.
The start-up of new MariaDB/MySQL container + creation of the initial user specified via the
MYSQL_*
variables can take about ~4-6s even in a relatively capable/fast environment:MariaDB container startup log with timestamps
When attempting a fully automated Nextcloud installation (i.e. populating a
NEXTCLOUD_*
variables in Compose), this can trigger a failure of the install attempt the first time around. This generates a scary looking error before we retry 10 seconds later:Scary stack trace if database container happens to not be fully initialized yet
Yes, we retry it 10s later and it all works out, but we can avoid this entirely by doing the delay before we even hit the retry cycle.
This PR: