-
Notifications
You must be signed in to change notification settings - Fork 23
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
Waiting for PostgreSQL database to become available... #7
Comments
I guess you are running the app on M1/M2 Mac? The postgres docker image we use is Could you please update the Thx. |
Thank you for your prompt reply. Unfortunately that does not appear to have fixed the issue. Here is the updated docker-compose output:
|
I did some research on this issue and figured it out Why this issue happenOn apple silicon, we got Postgresql SCRAM authentication problem? so the program hang with "Waiting for PostgreSQL to become available" message. SolutionWe can use Rosetta to make our program work with "linux/amd64" instead of the "arm64" Below are the steps:
And then run command below
I already tested it on real M1 Mac and it worked. Thx |
I can confirm that this worked for me too. I did have to change the docker-compose.yml back to how it is in the repo. Thanks for the help. |
I get Error response from daemon: image with reference django_celery_example_celery_flower was found but does not match the specified platform: wanted linux/amd64, actual: linux/arm64/v8 |
What is your OS? Thx. |
Latest os with M2 from apple. Thanks |
Changed the os architecture from image line, suggested from above. Same problem? Waiting.. for sql |
You need to remove your docker containers and docker images for a clean start https://stackoverflow.com/questions/44785585/how-can-i-delete-all-local-docker-images And then
|
Yes, docker system prune -a Done that |
is working on my side. |
A far better solution is to use Here is what is happening and you can see this stack overflow question which is the reason why our code was failing |
Be wary of using rosetta.It is a virtualization layer and as such can have a dramatic impact on performance. For minor projects you might not notice it, but for larger or more intense projects it can turn a 10 minute build process into something that takes longer than an hour. And once it is installed it is tedious to manage rosetta vs. native environments. Before resigning to installing rosetta, exhaust all your options using the |
Purchased the course (very well done!) but I'm unable to successfully run the docker container as posted in this repo. The individual services appear to all start but the services dependent on the PostgreSQL database complain about not being able to connect to the service. Below is the output from my attempt:
Perhaps I missed a step in the container setup?
The text was updated successfully, but these errors were encountered: