[forwardport]populate resolv conf from right location for multipod#2604
Merged
helsaawy merged 1 commit intomicrosoft:mainfrom Feb 18, 2026
Merged
[forwardport]populate resolv conf from right location for multipod#2604helsaawy merged 1 commit intomicrosoft:mainfrom
helsaawy merged 1 commit intomicrosoft:mainfrom
Conversation
populate resolv conf from right location(virtual pod dir) for virtualpod. issue: resolv.conf not getting populated with dns info incase of multi pod. cause: populating from wrong sandbox location fix: fix the read location (cherry picked from commit e8194749b14e96478d0e1ad15e07e71b7b7b5440) Signed-off-by: Hamza El-Saawy <hamzaelsaawy@microsoft.com>
jiechen0826
approved these changes
Feb 18, 2026
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.
populate resolv conf from right location(virtual pod dir) for virtualpod.
issue: resolv.conf not getting populated with dns info incase of multi pod.
cause: populating from wrong sandbox location
fix: fix the read location
(cherry picked from commit e8194749b14e96478d0e1ad15e07e71b7b7b5440)