Yay! 5 months after 16.04 release it started to work in Vagrant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
To
This image was made 3 hours ago while bug fix was released only 1 hour
ago. Is there a way to trigger image build again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (
Oh looks like someone has already filed it: https://bugs.launchpad.net
/cloud-images/+bug/1621393
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565985
Title:
vagrant vb ubuntu/xenial64 cannot mount
This is probably because /etc/resolv.conf is not a symbolic link to
/run/resolvconf/resolv.conf but is an empty file instead.
Also /etc/resolv.conf doesn't have a root write permission which is
probably the root cause of this problem
--
You received this bug notification because you are a member
Is it just me or the new 20160907 image has broken networking? It seems
to fail all DNS queries: `ping 8.8.8.8` works but `ping google.com`
fails with "unknown host" error.
STR:
$ vagrant init ubuntu/xenial64
$ vagrant box update
$ vagrant up
$ vagrant ssh
$ ping google.com
Result:
ping: unknown
The last update of ununtu/xenial64 image on Atlas was 7 days and it is
still broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565985
Title:
vagrant vb ubuntu/xenial64 cannot mount synced folder
