Set uid of user fluent at runtime #60
Merged
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
Member
|
Feature is good but I don't have an experience of dumb-init and gosu software. |
Contributor
Author
Member
|
I see. I don't have an experience with these tools, so |
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.
I reworked the docker image to allow setting the uid of the user fluent at runtime
and handle file ownership to avoid problems with host mounts.
The image now supports setting the uid of fluent with the env FLUENT_UID (defaults to 1000).
The envs FLUENTD_OPT and FLUENTD_CONF are still supported but the image can now be run with fluentds CLI parameters.
I added dumb-init and gosu as init system and to handel the user switching.
Changes:
If want to merge this pull request upstream let me know and i will add documentation.