Use a named Docker volume to better persist data #3592
Merged
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
This enables the use of defaults with variable interpolation. Followed procedure documented at https://docs.docker.com/compose/compose-file/compose-versioning/#version-1-to-2x
Otherwise, `docker-compose down' or otherwise removing the postgres container leaves orphan volumes that will not be reattached automatically.
|
Sweet, thank you! |
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.
Goal: Keep the database data around beyond the life of the DB container, and automatically attach it to new DB containers.
Without this,
docker-compose downor otherwise removing the postgres container leaves orphan volumes that will not be reattached automatically.Based on #3590 to avoid conflicts.