-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time delay vs wait-for-it for startup order #101
Comments
Not a bad idea. I'll take a closer look. I assume you know this, but in the meantime, you can also use the Obviously, neither of those options are better than something that checks actual connectivity, so perhaps Contributions are always welcome too! |
Sounds good. I'm closing in on completing this myself. I'll submit a PR soonest |
Current Behavior
In the docker documentation for controlling startup order, they recommend using (among others) wait-for-it. Currently the only available method for controlling startup order is a time-based timeout
Expected Behavior
Optionally support using network-based startup order control using wait-for-it
The text was updated successfully, but these errors were encountered: