Repository navigation
Run as UID/GID 1004 by default; release 0.1.1 - #2
Merged
Merged
Conversation
The image's dbbackup user is now 1004:1004 (previously UID 10001 with an auto-assigned GID of 999), matching the CronJob's securityContext, the restore Job example and the test stack. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Summary
dbbackupuser is now 1004:1004. Before, it was UID 10001 with an auto-assigned GID of 999, which didn't match the documented 10001:10001.securityContext, the restore Job example indocs/restore.md, and the test stack's tmpfs ownership.newTag, docs image references).Existing deployments that set
runAsUser/runAsGroupexplicitly are unaffected.Test plan
idin the image reportsuid=1004(dbbackup) gid=1004(dbbackup), anddbbackup --versionreports 0.1.1🤖 Generated with Claude Code