> On Jun 19, 2016, at 7:51 PM, Robert Hafner <email address hidden> wrote: > > In your VagrantFile use the config.vm.hostname option to specify a > hostname- > > config.vm.hostname = "vagrant"
Still get the error.
config.vm.define "testing_xenial64" do |testing_xenial64| testing_xenial64.vm.box = "ubuntu/xenial64" config.vm.network "public_network", bridge: "en0: Wi-Fi (AirPort)", auto_config: true config.vm.hostname = “ubuntu-xenial"
$ vagrant up --provision testing_xenial64 <snip>
The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!
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
-- Bob Tanner <email address hidden> | Phone : 952-943-8700 http://www.real-time.com, Linux, OSX, VMware, Windows | Fax : 952-943-8500 Key fingerprint = 9906 320A 8BB6 64AD 96A7 7785 CBFB 10BF 568B F98C
> On Jun 19, 2016, at 7:51 PM, Robert Hafner <email address hidden> wrote:
>
> In your VagrantFile use the config.vm.hostname option to specify a
> hostname-
>
> config.vm.hostname = "vagrant"
Still get the error.
config.vm.define "testing_xenial64" do |testing_xenial64| xenial64. vm.box = "ubuntu/xenial64" vm.network "public_network", bridge: "en0: Wi-Fi (AirPort)", auto_config: true vm.hostname = “ubuntu-xenial"
testing_
config.
config.
$ vagrant up --provision testing_xenial64
<snip>
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
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
-- www.real- time.com, Linux, OSX, VMware, Windows | Fax : 952-943-8500
Bob Tanner <email address hidden> | Phone : 952-943-8700
http://
Key fingerprint = 9906 320A 8BB6 64AD 96A7 7785 CBFB 10BF 568B F98C