Small fix: allow the vault process to write in /var/log #1
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
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.
Since in the vault:1.4.0 docker image the vault process is executed using the unprivileged vault user (uid 100 / gid 1000) the vault process cannot write its logs in
/var/log.This commit fixes that by running a
chmod 777to `/var/log/ before enabling the audit logs. 777 is a bit too much generours maybe, but for the small scope of the demo is not a big deal.This commit also introduces a
.gitignorefile that hides thelogs/directory and temporary files.