This is a docker issue by the looks of it. Are the...
# pact-python
e
This is a docker issue by the looks of it. Are there some log messages around the broker app start up?
t
Thanks for replying @Elliott Murray Here are the log messages for the broker when I do a
docker-compose up
:-
e
Pact broker clearly didn't start and it looks like that you have an issue with the postgres connection. There are a few ways to investigate this but at it's heart when you do
Copy code
docker-compose up
you should be able to log into the broker which IIRC is localhost:8080. I suspect postgres instance didn't start so work back from that (assume you don't have something on port 5432 already?)
It's really a docker question not a pact question so if you have someone on your team who knows that ask them to help you debug it
t
Okay. When I do a docker ps on a successful `docker-compose up`I get the following response(attached) but the docker connection exception persists on running the pytests for consumer.
e
Why is postgres up for 12 minutes but your broker for 24 seconds?
t
I am not sure. Postgres was healthy in the first attempt itself. Does it matter?