Allow influxdb to run as a configurable uid/gid #389
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 wanted to configure
influxdb
to run under a particular uid/gid (non-root) that was different than 999:999 that comes pre-configured in the container. Using--user
with docker didn't yield the desired results as it ended up not having permissions to access the data volume I supplied.With this change
entrypoint.sh
still runs as root and sets things up ifINFLUXDB_RUNAS_USER_ID
andINFLUXDB_RUNAS_GROUP_ID
variables are provided. After that, it usesgosu
(if applicable) to correctly downgrade to the influxdb user and group (now set to the correct uid/gid) before runninginfluxdb
.I did some local testing, but being my first attempt at a contribution, I'd love to hear more about how to validate this change further.