Skip to content
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

NO resolv.conf in kvm zone #298

Closed
marcheschi opened this issue Nov 17, 2017 · 4 comments
Closed

NO resolv.conf in kvm zone #298

marcheschi opened this issue Nov 17, 2017 · 4 comments
Assignees
Labels

Comments

@marcheschi
Copy link
Contributor

Hi
I tried to make a kvm zone using ubuntu-certified-17.10 image from Smartos repos.
The kvm zone is created successfully but without the /etc/resolv.conf file.
Thank you
Paolo

@dn0 dn0 added the support label Nov 17, 2017
@dn0
Copy link
Member

dn0 commented Nov 17, 2017

Hi Paolo,

Thank you for the information. These are not our official images, but we will try to reproduce the problem and then let you know if it can be fixed.

/etc/resolv.conf should be configured properly in our KVM images (usually set to the VMS_VM_RESOLVERS_DEFAULT DC setting.

@dn0 dn0 added this to the 2.7.0 milestone Nov 17, 2017
@dn0
Copy link
Member

dn0 commented Nov 17, 2017

Confirmed.
/etc/resolv.conf is correctly configured in the ubuntu-certified-16.04 image.
In ubuntu-certified-17.10 it stopped working probably due to some changes in cloud-init.

We will try to fix this in the next release.

Thank you for letting us know.

@dn0 dn0 added bug and removed enhancement labels Nov 20, 2017
@dn0 dn0 removed this from the 3.0.0 milestone Nov 21, 2017
@dn0 dn0 self-assigned this Nov 21, 2017
@dn0
Copy link
Member

dn0 commented Nov 21, 2017

Hi Paolo,

Originally, I was thinking that we can fix this by adding some metadata for cloud-init. Howerver, this is something that needs to be fixed in the image.

After playing around with the ubuntu-certified-17.10 image, I found that /etc/resolv.conf is a broken symlink to ../run/resolvconf/resolv.conf. There are at least two options to fix this:

  • rm -f /etc/resolv.conf; ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf (the systemd-resolved service maintains /run/systemd/resolve/resolv.conf from the first boot)

OR

  • apt-get install resolvconf

I've sent the information to the smartos-discuss mailing list.

@dn0 dn0 closed this as completed Nov 21, 2017
@dn0
Copy link
Member

dn0 commented Feb 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants