mirror of
https://github.com/run-llama/sec-insights.git
synced 2026-07-01 20:24:03 -04:00
Error when running docker compose up
#5
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jpzhangvincent on GitHub (Sep 9, 2023).
Got this error message when running the command
docker compose up. It seems it's complaining the server connection? How to troubleshoot this issue? Thanks!@sourabhdesai commented on GitHub (Sep 9, 2023):
Hi @jpzhangvincent , yeah this is an annoying issue :/ For now I'd give you the same recommendation I gave someone else that ran into this problem on this issue. I'll look into seeing what I can do to work around this soon
@siddarthreddygsr commented on GitHub (Sep 10, 2023):
I would like to work on this issue.
@JeroenJADS commented on GitHub (Sep 11, 2023):
This doesn't actually matter to much. After you've done a
docker compose up, just pressctrl + cand runmake runshould work!@siddarthreddygsr commented on GitHub (Sep 11, 2023):
Yeah that should do the job because it spins up the database and the localstack individually. As db is spun first it would have enough time to start before the localstack loads and tries to connect to connect to the database. But using
docker compose upand checking if the DB is ready while connecting to it is the right way, especially if you're considering scaling.@sourabhdesai commented on GitHub (Sep 11, 2023):
@siddarthreddygsr @JeroenJADS @jpzhangvincent we just merged in @siddarthreddygsr 's PR for this issue. That should get rid of the race condition between the db container and the backend container as the backend container will just wait until the db is ready for connection!
Thanks @siddarthreddygsr for taking this up!
@cosminro commented on GitHub (Sep 11, 2023):
I still get the error, just rebased