This still doesn't resolve the issue. In order to function, a chroot
needs /etc/resolv.conf copied from the host's normal /etc/resolv.conf,
but because of the current implementation, the host's /etc/resolv.conf
content will always be "nameserver 127.0.0.1" which is entirely useless
inside the chroot.
** Changed in: resolvconf (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922578
Title:
please remove 'resolvconf' from ubuntu-minimal Depends
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/922578/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
