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

Race condition running docker-compose #267

Closed
avantgardnerio opened this issue Sep 23, 2022 · 0 comments · Fixed by #268
Closed

Race condition running docker-compose #267

avantgardnerio opened this issue Sep 23, 2022 · 0 comments · Fixed by #268
Labels
bug Something isn't working

Comments

@avantgardnerio
Copy link
Contributor

Describe the bug

When Ian ran docker-compose up --build, he ran into several errors:

[ballista-executor_1   | Error: Could not connect to scheduler
[ballista-executor_1   | 
[ballista-executor_1   | Caused by:
[ballista-executor_1   |     0: transport error
[ballista-executor_1   |     1: error trying to connect: tcp connect error: Connection refused (os error 111)
[ballista-executor_1   |     2: tcp connect error: Connection refused (os error 111)
[ballista-executor_1   |     3: Connection refused (os error 111)

and

[ballista-client_1     | /bin/sh: 0: cannot open sleep: No such file

and

[ballista-scheduler_1  | Starting nginx to serve Ballista Scheduler web UI on port 80
[ballista-scheduler_1  | nohup: failed to run command 'nginx': No such file or directory

We should fix these issues.

To Reproduce

Run the above command.

Expected behavior

A working docker composition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant