Closed BookOfGreg closed 5 years ago
The db logs are fine, they're just saying that the schema_info table does not yet exist (as you would expect the first time).
The RVM error comes up all the time as well, it can be ignored.
Does it work when you don't change the ports?
Opening another tab and using curl -v http://localhost:80
or 8080
makes no difference and doesn't trigger anything additional in the logs. Do I need to manually trigger the database to setup when using the docker-compose?
Sorry for the daft question, I feel like I child when I can't solve these simple things myself, I'm probably missing something obvious. I really appreciate your time helping me.
Not sure what the difference is but it's working now. Could be that I cleared a load of disk space on the docker host. but honestly couldn't pin it down.
Pre issue-raising checklist
I have already (please mark the applicable with an
x
):Software versions
Expected behaviour
When I use the example docker-compose here I should have a working pact-broker.
I changed the nginx ports to the following as I am not running this as root and do not need SSL yet:
Actual behaviour
It appears Passenger shuts down on startup but the container doesn't finish?
I also believe the postgres DB has never been migrated.
Edit: If I'm using a sqlite db I get a similar issue, but more debug logs:
Steps to reproduce
docker-compose up on the example docker-compose.
Relevent log files
Please ensure you set logging to
DEBUG
and attach any relevant log files here (or link from a gist).