The volume path for db-data was wrong. needed data sub-folder. Without that wasn't persisting the db on stop of container. #175
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
…t that wasn't persisting the db on stop of container.
|
Hi, thanks for the PR. Looks good! |
|
Hmmm, I feel this one. Happened to me once with a Gitlab Postgres container ... lost a couple of days worth of data :-( |
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.
In using this docker-compose found that because the db-data volume was different to that in the postgres:10-alpine dockerfile the system did not persist data between down and up of docker-compose. Added /data to volume path and now all works.