feat: no more special UID, only GID 0 - #197
Open
dotconfig404 wants to merge 2 commits into
Open
Conversation
dotconfig404
force-pushed
the
feat/gid0-arbitrary-uid
branch
from
August 14, 2026 13:57
4fca3be to
0765bd9
Compare
Signed-off-by: dotconfig404 <dotconfig@krutt.org> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
dotconfig404
force-pushed
the
feat/gid0-arbitrary-uid
branch
from
August 14, 2026 14:07
0765bd9 to
86a2bff
Compare
Signed-off-by: Anthony Somerset <anthony@sts.io>
anthonysomerset
approved these changes
Aug 15, 2026
anthonysomerset
left a comment
anthonysomerset
left a comment
Contributor
There was a problem hiding this comment.
this looks good to me, just a few markdown lint errors to clear
rwaffen
requested changes
Aug 27, 2026
|
|
||
| UID is changed from 1001 on alpine and 999 on ubuntu to 64604. | ||
| If you already deployed the containers with mounted volumes, you HAVE to change the ownership of these volumes and the files underneath. | ||
| The container runs with **group 0** and works under **any UID**. File access is granted exclusively through group 0, and the UID of files on mounted volumes does not matter. There is no `puppet` service account in the image anymore. |
Member
There was a problem hiding this comment.
pls do "one sentence one line" style.
| # Migrations | ||
|
|
||
| ## V8.12.0 -> V8.13.0 | ||
| ## Coming from a fixed UID release |
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
3 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.
Short description
As discussed in slack, this PR should make the access model much clearer. GID 0 is to be used for volumes and generally for file access, any UID can be used.
This does not fundamentally change anything that wasn't implemented already since
9e73538
but since the restructure of the images there was some regression, for example the addition of a script that sets permissions when a certain UID is used. Instead of making a specific UID special a fix should be applied across all UIDs the same.
Hopefully this PR will make it easier to maintain the repo.
Checklist
I have:
Signed-off-byannotation to each of my commitsGenerated-byorAssisted-byannotations to each of my commits created with the help of an AI agentEDIT: wrong commit/PR mentioned