-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--set
with .dns
doesn't always seem to work
#1940
Comments
--set
with .dns
doesn't seem to work --set
with .dns
doesn't always seem to work
@pmalek Which template are you using ?? |
i encountered same behavior, after digging little into source code it looks like, if vmType == VZ, then it's always using args.SlirpDNS (which is gatewayIp) to generate user-data
not sure whether it's intended behavior. from the source Line 268 in 391133d
always go into first if condition branch
|
@neowu Yes that's the issue. Thanks for the analysis. |
@balajiv113 I am willing to submit PR, though I haven't worked on Go project before :) just need to make sure the expected behavior, do we always want to use DNS settings if existed, something like
|
Fixed as part of #1962 |
Description
I use the following set of flags
Recently (with b5aa0dd) discovered that the dns setting doesn't always work as expected. I'm not sure what should be the effect of that setting but sometimes it does put
192.168.1.250
in/etc/resolv.conf
and sometimes doesn't.What should be the effect of that setting?
The text was updated successfully, but these errors were encountered: