docs: Explicit restrictions of atlantis user apply to the --data-dir
flag
#2908
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.
what
As the atlantis user is restricted to the home directory of atlantis (
/home/atlantis
), setting the--data-dir
flag to another path will result in a permission denied error.I've updated the documentation to be more explicit on this common pitfall.
why
This is a common made mistake as we nowhere document how restricted the atlantis user is, I had to look at the docker-base to understand why, what and where the atlantis user permissions were applied.
tests
references
--data-dir
is not/home/atlantis
results in permission denied #2903