ubuntu/xenial vagrant box has /etc/hosts misconfigured

Bug #1568447 reported by Adam Chou on 2016-04-10
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
cloud-images
Undecided
Unassigned

Bug Description

I'm using the ubuntu/xenial-64 vagrant box from this location: https://vagrantcloud.com/ubuntu/boxes/xenial64

Trying to start it up gives me this error:
hostname -f

Stdout from the command:

Stderr from the command:

sudo: unable to resolve host ubuntu-xenial
mesg: ttyname failed: Inappropriate ioctl for device
hostname: Name or service not known

Logging into the box and running hostname -f also returns the same error.

cat /etc/hostname shows ubunu-xenial

ubuntu-xenial should also be set in /etc/hosts, but is not.

Adding ubuntu-xenial to 127.0.0.1 will allow the hostname -f command to execute correctly.

Dmitry R (romanenko-dmitry-a) wrote :

I think this bug is critical.
Can't use Ubuntu 16.04 in vagrant.

Bobby Naydenov (bnaydenov) wrote :

I am reproducing the same issue with following versions used:

OS Host: Mac El Capitan - 10.11.4
Virtualbox: 5.0.20 r106931
Image: ubuntu/xenial64 (virtualbox, 20160429.0.0)
Vagrant 1.8.1

Any ideas what is root cause about this issue?

Nayeem Syed (developerinlondon) wrote :

i also have the same problem.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers