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
I did a little more digging on this. Looks like there is a silent failure if there is already a postgres server on port 5432. Changing docker-compose.dev.yml to have:
solved the issue. I also had to do this for the nginx portion, since I already have an nginx service listening on 80. Surprisingly, the nginx container was noisy when the daemon errored: Error response from daemon: driver failed programming external connectivity on endpoint danswer-stack-nginx-1 (9410c13fee582fdf3f7f214dc226b2a500ffc7091537320bc54c72e04f13e3b8): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use
while the relational db (postgres) container was not.
The quickstart instructions recommend two different approaches:
docker compose -f docker-compose.dev.yml -p danswer-stack up -d --pull always --force-recreate
docker compose -f docker-compose.dev.yml -p danswer-stack up -d --build --force-recreate
These work almost all the way, but get stuck while trying to start
danswer-stack-relational_db-1
There is no printed error, but the container never starts correctly.
Docker version:
Docker version 24.0.2, build cb74dfc
The text was updated successfully, but these errors were encountered: