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.
I updated this project for my own use, and I prefer using named volumes because of they are less problematic with UIDs, are "file path separator aware" when using absolute paths and allow easier backup management. Named volumes also allow initial container content to be added to this folders, meanwhile host volumes force to add all need required content in local path (because of that Solr6 logs cannot be accessed in original version of this project).
The main disadvantage is the need of use of gdiepen/volume-sharer, or similar one, to access file in volumes (at least in Windows, in Linux could be accessed directly in
/var/lib/docker/volumes
but the problems with UIDs would appear using this direct path).README.md was updated to show these changes, but my English needs a peer-review.