[Bug 1561250] Re: Xenial vagrant image is missing its hostname in /etc/hosts

GGeorg georg-ubuntu.com at glas.eu.org
Wed Jul 6 10:32:22 UTC 2016


@Dan: Thx for your feedback i checked the diff at:
https://i267500511.restricted.launchpadlibrarian.net/267500511/3d1e0c04
-3a0e-11e6-bd2f-002481e91f22.txt?token=4gc9PKPGwls2N9trTB0D26bj1nLqDrbv

Absolutly see your point in the buildds infrastructure :)


Here is my feedback:

* libnss-myhostname will fix _this_ problem but might break things for
other users, i would not recommend going this route as it changes an
already released package list and image. Bad for LTS i would suggest to
use the existing and already proven cloud-init way to handle /etc/hosts
like mentioned above - this has been proven to work for aws and other
cloud providers.

* If the future image has 557 MB vs 282 MB at the current - than please
dont fix it :) seriously if a box update takes twice the time it took
before the change, the change is broken. Changeing all this for a LTS
breaks the idea of having lts.

cloud-images - in my point of view -  should contain only the bare
minimum, if the user wants additional software there are multiple ways
to do so in vagrant or to provide meta-data with cloud-init. Lets yust
see what hashicorp tells us todo:

https://www.vagrantup.com/docs/boxes/base.html

There are a special category of boxes known as "base boxes." These boxes
contain the bare minimum required for Vagrant to function, are generally
not made by repackaging an existing Vagrant environment (hence the
"base" in the "base box").

adding: virtualbox-guest-dkms and virtualbox-guest-utils 
       makes sense even so its not needed (user can install it with provisioner and add the mount point)
adding: 
       linux-headers-generic
       nfs-common
       python-apport
       puppet
       chef
       byobu
       juju
       ruby

will break stuff and is not needed - because were to stop ? next person
will request cfengine to be included ?! IMHO not a good idea - but yust
my 2 cents ..

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1561250

Title:
  Xenial vagrant image is missing its hostname in /etc/hosts

Status in cloud-images:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  The vagrant build for xenial is missing an in /etc/hosts. This
  generates an error when running sudo.

  ubuntu at ubuntu-xenial:~$ cat /etc/hosts
  127.0.0.1 localhost

  # The following lines are desirable for IPv6 capable hosts
  ::1 ip6-localhost ip6-loopback
  fe00::0 ip6-localnet
  ff00::0 ip6-mcastprefix
  ff02::1 ip6-allnodes
  ff02::2 ip6-allrouters
  ff02::3 ip6-allhosts
  ubuntu at ubuntu-xenial:~$ sudo echo see the error ^^^^
  sudo: unable to resolve host ubuntu-xenial
  see the error ^^^^
  ubuntu at ubuntu-xenial:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1561250/+subscriptions



More information about the foundations-bugs mailing list