Open tcanavan opened 5 years ago
Given this container works on standard Docker environments, this must mean there is something special about CF. We can't be expected to be experts in every runtime, have you done any digging that means you can give us something to look at?
Furthermore, we also now have an "edge" tag available that has a different runtime, it might be worth giving that a try also.
See #90
Could it be that our cloud foundry only supports https. Do I need also to install nginx as a reverse proxy?
This line: 2019-05-16T12:08:48.63+0200 [HEALTH/0] ERR Failed to make TCP connection to port 443: connection refused
suggests that whatever is externally monitoring the instance is doing a healthcheck on port 443. Port 443 isn't configured or exposed on the broker docker image (it's expected that you'll set up your own SSL configuration).
So, yes, you'll need to set up nginx yourself.
Pre issue-raising checklist
I have already (please mark the applicable with an
x
): xSoftware versions
Expected behaviour
Container starts
Actual behaviour
Tries to start but gets the following error
Steps to reproduce
cf push smt-pact-broker --docker-image dius/pact-broker
Relevent log files
Please ensure you set logging to
DEBUG
and attach any relevant log files here (or link from a gist).