-
Notifications
You must be signed in to change notification settings - Fork 24
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
wait-for-it.sh
fails with Exit Code 127
#94
Comments
I built a
but in my local development environment it keeps reporting me an execution error with "file not found":
|
@bodo-hugo-barwich is it possible that the file really doesn't exist locally? Maybe this is not running from the correct directory? |
I see a difference between the command that succeeds:
and that one that fails:
in where the quotes are set.
So, this seems me to be the result of the
I understand I also searched in the project where the "morbo" command is defined.
I see that So, I changed
Now the startup sequence shows:
I also checked the changes in
To check whether the quotes would really make such a difference I imported the
Relaunching the
|
Were the quotes in the |
According to the latest Automated Tests in GitHub the components are now up and operative:
Automated Test Component
@oalders are you interested in keeping this test for the project since it is more conclusive than the existing |
Yes @bodo-hugo-barwich, that looks to be quite helpful. |
On
master
branch serviceapi
reports an Exit Code127
withdocker-compose up -d api
:The expected state should be:
The text was updated successfully, but these errors were encountered: