zerstoeren
commented
6 years ago When executing the command to run the container, are you exposing the postures port?
You should see --expose and -p xxxx:xXxX if so.
Also, check the postures configuration file and make sure that localhost is allowed to connect. There migh t be an extra postures config parameter missing. I am guilty of this a lot.
On Jan 28, 2018 9:30 AM, "Josiah Eleazar T. Regencia" < notifications@github.com> wrote:
So tried fixing the problem in the previous report. Still haven't gotten anywhere significant. Tried installing postgres inside Dockerfile.test, doesn't seem to work well. It gives an error. Tried changing the port and the host still resulted in
psycopg2.OperationalError: could not connect to server: Connection refused Is the server running on host "172.17.0.1" and accepting TCP/IP connections on port 5433?
Not really sure what it means. But I'll find a way. Maybe has something to do with running postgres. Haven't seen anything about running postgres using docker yet.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Doveps/mono/issues/81, or mute the thread https://github.com/notifications/unsubscribe-auth/AGbogr6VI2IOHbLE9ol67N7-XL-_-SE2ks5tPIR6gaJpZM4Rvtqt .
JosiahRegencia
So tried fixing the problem in the previous report. Still haven't gotten anywhere significant. Tried installing postgres inside Dockerfile.test, doesn't seem to work well. It gives an error. Tried changing the port and the host still resulted in
psycopg2.OperationalError: could not connect to server: Connection refused Is the server running on host "172.17.0.1" and accepting TCP/IP connections on port 5433?
Not really sure what it means. But I'll find a way. Maybe has something to do with running postgres. Haven't seen anything about running postgres using docker yet.