Fix Postgres compose volume mount - #13
Draft
cursor[bot] wants to merge 1 commit into
Draft
Conversation
Co-authored-by: Bruno Medeiros <bruno.do.medeiros@gmail.com>
This file contains hidden or 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
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.
Summary
pgdatanamed volume at Postgres' actual default data directory (/var/lib/postgresql/data).Bug and impact
pgdatavolume but mounted it at/var/lib/postgresql/data2while the official Postgres image writes database files to/var/lib/postgresql/databy default.Root cause
PGDATAlocation without also settingPGDATAto match.Fix and validation
docker-compose.ymlto mountpgdataat/var/lib/postgresql/data./data2mount remains.docker compose configcould not be run in this environment because Docker is not installed (docker: command not found).