Run in privileged remote containers #77046
Merged
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.
/assign @mikedanese @cblecker
Fixes #77040
Fixes #77041
Note that the non-rbe job runs in a privileged container whereas the rbe job runs unprivileged.
https://github.com/fejta/test-infra/blob/26216e434963dd74dd1156d276a5aaf2b13b06b8/config/jobs/kubernetes/sig-testing/bazel-build-test.yaml#L133-L191
Looks like the two jobs above must run in a privileged container, but we can limit this privilege to the remote execution and keep the prow container unprivileged.
ref kubernetes/test-infra#12282