Skip metadata interception in non-root containers#110
Merged
ptone merged 3 commits intoGoogleCloudPlatform:mainfrom Apr 11, 2026
Merged
Skip metadata interception in non-root containers#110ptone merged 3 commits intoGoogleCloudPlatform:mainfrom
ptone merged 3 commits intoGoogleCloudPlatform:mainfrom
Conversation
mfreeman451
force-pushed
the
fix/nonroot-metadata-interception
branch
from
c54ea37 to
2cd7be8
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
Problem
In non-root containers, sciontool cannot install the iptables-based metadata interception rules. The metadata env vars are still the primary mechanism there, so attempting interception just produces noisy, misleading warnings without helping agent behavior.
Validation
go test ./pkg/sciontool/metadata