Show that a pod's containers each run as their own unprivileged user - #876
Closed
MayCXC wants to merge 1 commit into
Closed
Show that a pod's containers each run as their own unprivileged user#876MayCXC wants to merge 1 commit into
MayCXC wants to merge 1 commit into
Conversation
Nothing in the pod requires its containers to be root, and each carries its own process configuration, so they can run under different users without anything else being arranged.
MayCXC
force-pushed
the
pod-rootless-containers
branch
from
August 27, 2026 20:47
3893c93 to
735fe4e
Compare
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
Nothing in the pod requires its containers to be root, and each carries its own process configuration, so they can run under different users without anything else being arranged. The integration suite says so now.
Motivation and Context
A pod's containers share a machine, and the question of whether sharing one constrains who they run as is worth an answer that a change can break. The existing pod tests all run root, so the property held by accident rather than by assertion.
Testing
make integrationwith the new case: the pod comes up with its containers under distinct unprivileged users and each reports the user it was given.Type of Change