-
Notifications
You must be signed in to change notification settings - Fork 644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start Postgres using PropertyConfigHandler #451
Comments
Thanks, will try to reproduce it. |
I had a different issue with your setup (with tcpWait stuff added accidentally), which I just fixed and it works now for me. I just pushed a 0.15.2-SNAPSHOT to maven central, could you try this ? |
Yes, with this snapshot Postgres starts up successfully. This is great! However, the |
cool, will check that. btw, do you think it would be a good idea to allow the inclusion of a property file directly in the |
Yes, that would certainly be nice to have, but you would have to include some implementation of substituting variables such as |
Shouldnt be that hard, Maven has an internal service who does property resolution. I will give it a shot. |
Fixed in 0.15.2 |
When I try to launch the official Postgres image using properties configuration, it fails with the following error:
Using debug logging, I have extracted this as the call made to Docker when the error occurs:
One thing that stands out is that there are empty arrays being sent for Cmd, Entrypoint and VolumesFrom. These are not present when running shootout-docker-maven.
For my project, I have these properties in (project-root)/docker-setup/postgres.properties:
My maven config looks like this:
The text was updated successfully, but these errors were encountered: