You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 text was updated successfully, but these errors were encountered: