Repository navigation
Hand Teku and Nimbus data dirs to uid 1000 before start - #490
Merged
Merged
Conversation
|
OisinKyne
approved these changes
Oct 5, 2026
KaloyanTanev
added a commit
that referenced
this pull request
Oct 5, 2026
`nimbus/run.sh` ran `rm -rf /home/user/data` on every start, which also wiped the Nimbus VC's slashing protection DB (`validators/slashing_protection.sqlite3`). It now removes only the previously imported keys (`secrets/` and `validators/0x*`) before re-importing them, matching charon-distributed-validator-cluster. Before #490 the wipe mostly failed silently, because uid 1000 couldn't write to the root-owned `./data/vc-nimbus`. Now that #490 hands that directory to uid 1000, it succeeds on every restart.
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
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.
Teku and Nimbus images run as uid 1000, but docker creates missing bind mount directories as root, so on a fresh setup neither could write to
./data/vc-tekuor./data/vc-nimbus. Both containers now start as root only long enough forrun.shto hand the data directory to uid 1000 (chown -R 1000:1000, mode700, which Nimbus requires). The script then re-runs itself as uid 1000 withsetpriv, so key import and the client itself run unprivileged. This works whatever the host user's uid is.Teku gets a new
teku/run.shthat ends withexec /opt/teku/bin/teku "$@", and itscommand:is unchanged. Nimbus'srun.shis now mounted at/home/user/run.shand set asentrypoint:, outside the data directory, so thechowndoesn't change the owner of the tracked file on the host. The composeentrypoint:overrides theENTRYPOINTof nimbus images that operators have already built.Tested on a host user with uid 1001: the data directories were missing, root-owned, or owned by 1001 at
700, and each ended up1000:1000at700. Teku's Java process and the Nimbus VC ran as uid 1000, and the scripts on the host kept their owner.Fixes #357