chore: add proactive config writability checks to entrypoint scripts#20
Merged
Conversation
simonfr
force-pushed
the
chore/verify-config-writable
branch
3 times, most recently
from
03b1021 to
6d510ae
Compare
simonfr
force-pushed
the
chore/verify-config-writable
branch
from
6d510ae to
a474ca3
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds a proactive
verify_config_writablecheck in the container entrypoint scripts (docker-entrypoint.shandstandalone-entrypoint.sh).If the volume configuration has permission/ownership issues that would lead to
attempt to write a readonly databaselater in the boot process (such as reported in #17), the entrypoint will now clearly warn the user in the docker logs with troubleshooting steps (chown, volume mount check, etc.).