-
-
Notifications
You must be signed in to change notification settings - Fork 106
Postgres 18 #365
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
Postgres 18 #365
Conversation
|
Whats the entire output of an initial |
|
|
Atm it looks like all tests fail because the |
Have added a change that tries to ensure the container is running after create |
|
Yeah create still exits 0. I'll have to take a look at this tomorrow and see whats going on locally. |
|
I see now that it's the call in so the following call in This |
|
We can use the |
This gets bumped during a release
|
Thanks for the pull request! |
Adds support for Postgres 18 by adding conditional logic to set the data volume path differently for before/after v 18, as guided by https://hub.docker.com/_/postgres
Fixes #364
Replaces #358 / #367
Not sure if this needs to be fixed or not, but there's a subtle functional change in the result with this code as is.
dokku postgres:startto re-start serviceThis appears to be because of the logic in
https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh#L360
v17 triggers the path with message output
v18 triggers the path with message output
and stops the container.