fix(k8s): use UID 1001 to align with upstream#28
Merged
Conversation
Ubuntu 24.04 ships with a built-in 'ubuntu' user at UID 1000. Upstream moved to UID 1001 to avoid needing to delete this user. Aligning our branch with this change simplifies future merges. Changes: - Dockerfile: agent user now UID/GID 1001 (no userdel needed) - k8s-workload-service: pod securityContext uses 1001 - initContainer chown uses 1001:1001
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.
Summary
ubuntuuser at UID 1000, so upstream moved to 1001 to avoid needinguserdelChanges
images/base.Dockerfile: agent user now UID/GID 1001 (removesuserdel ubuntuworkaround)k8s-workload-service.ts: pod securityContext uses 1001 for fsGroup/runAsUser/runAsGroupk8s-workload-service.ts: initContainer chown uses 1001:1001Test plan
./images/build.sh