Clarify proxy.user chown command #590
Closed
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
in the chown command, the number the user (e.g. 901:999) should match that defined in the docker-compose.yml file (proxy.user)
|
This was addressed during latest deployment changes. |
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.
In the chown command, the number the user (e.g. 901:999) should match that defined in the docker-compose.yml file (proxy.user).
If they don't match, it results in an error in starting the proxy server component.
As of most recent commit 74a716f8932a2233c942f5bca98b1b76ec2e7875 on master branch, the proxy.user in docker-compose.yml specifies 101:999, which is different than this documentation.