zachariahyoung commented 5 years ago

Pre issue-raising checklist

I have already (please mark the applicable with an x):

[x ] Confirmed this is the right place to raise the issue - only issues related to the Dockerization of the Pact Broker should be raised here. Issues related to the Pact Broker application itself should be raised in the Pact Broker project.
[ x] Upgraded to the latest Pact Broker Docker image OR
[ ] Checked the CHANGELOG to see if the issue I am about to raise has been fixed
[ ] Read the Troubleshooting page

Software versions

pact-broker docker version: f62083f7d787 -> Image ID
OS: Windows 10

Expected behaviour

Should be able to run docker-compose up from the provide docker compose file

Actual behaviour

$ docker-compose up pact_postgres_1 is up-to-date Starting pact_broker_app_1 ... error

ERROR: for pact_broker_app_1 Cannot start service broker_app: driver failed pro gramming external connectivity on endpoint pact_broker_app_1 (06f93d122fceeb62b8 a320ceea2d939c1ed3cde5285456dd00d23c52bafb0c6f): Error starting userland proxy: Bind for 0.0.0.0:80: unexpected error Permission denied

ERROR: for broker_app Cannot start service broker_app: driver failed programmin g external connectivity on endpoint pact_broker_app_1 (06f93d122fceeb62b8a320cee a2d939c1ed3cde5285456dd00d23c52bafb0c6f): Error starting userland proxy: Bind fo r 0.0.0.0:80: unexpected error Permission denied Encountered errors while bringing up the project.

Steps to reproduce

Reran the docker-compose up command several times. Got the same error message.

Relevent log files

Please ensure you set logging to DEBUG and attach any relevant log files here (or link from a gist).

bethesque commented 5 years ago

I believe this is likely to due to permissions issues with Windows and binding to restricted ports, rather than a specific issue with the Pact Broker Docker compose config. Please try googling for relevant terms and see what you get.