Make docker host-mounted volumes work #4
Conversation
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
added 3 commits
December 17, 2021 11:01
… start due to an empty volume /git/data
… start due to an empty volume /git/data
… start due to an empty volume /git/data
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 case docker host-mounted volumes are to be used, this does not work. The reason is that the Dockerfile creates some directories within /git/data, but this is a volume, meaning that when using host-mounted volumes, what was done during image creation is lost and the image fails to start. Doing the directory creation in the bootstrap shell script prevents this.
I believe there will be no difference in other use cases, such as with the provided dockec-compose file, though I have not specifically tested that.