Skip to content
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

entrypoint wait-for-it misconfigured - it will start regardless of the state of other containers #32

Open
dreadedhamish opened this issue Jul 12, 2023 · 1 comment

Comments

@dreadedhamish
Copy link

Currently the graylog container implements the wait-for-it script on startup, checking that opensearch etc... has started. Currently it will start the graylog container regardless of the state of the target container after the 15 second wait time.

The readme from the wait-for-it script mentions that this is expected behaviour, and that to turn give it a blocking function you need to add the --strict flag:

The subcommand will be executed regardless if the service is up or not. If you wish to execute the subcommand only if the service is up, add the --strict argument.

@dreadedhamish
Copy link
Author

As an alternative to using --strict you could use an infinite timeout:
--timeout=0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants