2025-03-05 Chronograf - master branch - PR 1 of 2 #787
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.
PR 781 was submitted on 2025-01-21 but is has now been over 40 days without any response. It isn't clear whether it is simply taking the time it needs to take, or if this is a signal that it will never be processed.
The basic problem occurs with Docker "bind mounts" which are the convention for IOTstack containers. If Chronograf launches from a clean slate, Docker will create
./volumes/chronografwith root ownership. Although the container launches as root, it does not take the opportunity to enforce its ownership conventions prior to downgrading its privileges to that of (internal) userchronograf(ID=999). The result is the container can't write to its persistent store, crashes and goes into a restart loop.This PR provides an augmented entry point script which sets ownership correctly prior to launching the
chronografprocess.This PR applies the patch for IOTstack users via a local Dockerfile.
It can be unwound if/when PR781 is processed.