xenial cloudimage with missing hostname on hosts
Bug #1573015 reported by
Luis Ferro
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Expired
|
High
|
Unassigned | ||
hostname (Ubuntu) |
Expired
|
High
|
Unassigned |
Bug Description
Install Vagrant / Virtualbox
On Terminal run:
$> vagrant init
Edit the Vagrantfile to change the box name from "base" to "ubuntu/xenial64"
Then on the terminal again do:
$> vagrant up
After installing do:
$> vagrant ssh
$> sudo su
You will get a message stating: "sudo: unable to resolve host ubuntu-xenial"
The reason for this message is because the entry on /etc/hostname (which have "ubuntu-xenial") doesn't exist on /etc/hosts
To Fix:
Edit the /etc/hosts:
$> sudo vim /etc/hosts (for instance)
And on the entry:
127.0.0.1 localhost
Change to:
127.0.0.1 localhost ubuntu-xenial
Changed in hostname (Ubuntu): | |
importance: | Undecided → High |
Changed in hundredpapercuts: | |
status: | New → Confirmed |
importance: | Undecided → High |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.