docs: Add caveat for ENV DMS_VMAIL_UID
value compatibility
#4143
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.
Description
This raises awareness of a compatibility issue found when troubleshooting: #4098 (comment)
I've not looked into it further but the actual
docker
user / group usage is a bit unclear (horrible choice given the project, not an easy thing to search for). This feature at least seems to work even when the UID fails, but that may be due to/var/mail
sticky-bit with group and thechown
, since thedocker
user will still have their GID adjusted. For reference I did document coverage on thedocker
/5000
user assignment and usage a while back: #3557Just updating documentation, so the mentioned error log item would still be present if the adjustment fails because a UID was selected that is already associated to another user (
/etc/passwd
).Type of change
Checklist
CHANGELOG.md