Use a Bookworm based Postgres image in Docker compose #1892
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pauloxnet
force-pushed
the
clean/docker-postgres
branch
from
8442fa8 to
e8a41f1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Alpine-based Postgres Docker image has some limitations compared to the standard one (eg: locale, extensions, ...), also I believe that the production version is not based on musl but on glibc.
I propose to use the standard version of the Postgres image in Docker compose to increase compatibility with the production system, having the same functionality locally without using too much more space since the standard version image is only a few megabytes larger than the Alpine one (eg: 142 MB vs 103MB).