This change will be backported to xenial, but only once we've heard that we've actually fixed it.
Robert, GGeorg, LoOoD, does the box I provided fix the issue? (Also, Robert, I really do understand the frustration but this wasn't actually as simple a fix as you seem to think; Vagrant boxes should have their hostname set dynamically at boot, which means you can't simply write out the hostname to /etc/hosts during the image build process. And when you add in to this the fact that a lot of behaviour that is clearly expected of Vagrant boxes isn't actually documented anywhere[0], any fix becomes time-consuming as you have to try and work out what the expected behaviour is by looking at other Vagrant boxes.) [0] Search for "host" in https://www.vagrantup.com/docs/boxes/base.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561250 Title: Xenial vagrant image is missing its hostname in /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1561250/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
