Add docker volume to db container #361
Closed
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 the manual instructions we are not creating a docker volume or mount path to have the database in a secure location. This is an issue when updating the container or when the default driver changed from aufs to overlay2.
The database container created using these instructions cannot be destroyed or re-created without data loss.
So I propose to add a step inside the manual for the creation of docker volumes beforehand, as we do with the docker-compose file.
and change the container creation accordingly