Well, one way to work around this would be to have a bootcmd change
/etc/resolv.conf to not be a symlink. resolvconf only modifies
/etc/resolv.conf if it is a symlink into ../run/resolvconf/resolv.conf .
that said, resolvconf should probably be able to do what you want it to
do and it might be best to just let it do its work.
It is possible, that cloud-init should do that for you if you specify
resolv_conf.
** Summary changed:
- unable to set resolve.conf
+ unable to set resolv.conf
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394224
Title:
unable to set resolv.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1394224/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
