Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@sameo
Copy link

@sameo sameo commented Mar 24, 2017

When pod sandboxes come with DNS settings, we build and bind mount a resolv.conf file into the pod sandbox rootfs.
In order for pod internal DNS to work, we have to propagate that mount point to all pod containers.

Fixes #402

Samuel Ortiz added 2 commits March 24, 2017 15:28
When we get a pod with DNS settings, we need to build
a resolv.conf file and mount it in all pod containers.
In order to do that, we have to track the built resolv.conf
file and store/load it.

Signed-off-by: Samuel Ortiz <[email protected]>
When a pod sandbox comes with DNS settings, the resulting resolv.conf
file needs to be bind mounted in all pod containers under
/etc/resolv.conf.

Signed-off-by: Samuel Ortiz <[email protected]>
@sameo
Copy link
Author

sameo commented Mar 24, 2017

cc @mcastelino

@mrunalp
Copy link
Member

mrunalp commented Mar 24, 2017

@sameo The fix looks fine. I will wait for the tests to go through. Thanks!

@mrunalp mrunalp added this to the 0.2 milestone Mar 24, 2017
@mrunalp
Copy link
Member

mrunalp commented Mar 24, 2017

LGTM

@mrunalp mrunalp merged commit 4cdc1a3 into cri-o:master Mar 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants