[Bug 1573015] Re: xenial cloudimage with missing hostname on hosts
Launchpad Bug Tracker
1573015 at bugs.launchpad.net
Wed Oct 6 04:17:32 UTC 2021
[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]
** Changed in: hundredpapercuts
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to hostname in Ubuntu.
https://bugs.launchpad.net/bugs/1573015
Title:
xenial cloudimage with missing hostname on hosts
Status in One Hundred Papercuts:
Expired
Status in hostname package in Ubuntu:
Expired
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1573015/+subscriptions
More information about the foundations-bugs
mailing list