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
or
Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 v-csc-78dab358b /tmp/vagrant-chef/1d140fd50fa8a0774caff0f697e00977/cookbooks The error output from the command was: mount: unknown filesystem type 'vboxsf'
And keep finding google results for these threads:
- https://github.com/mitchellh/vagrant/issues/6769
- https://bugs.launchpad.net/cloud-images/+bug/1568447
- https://askubuntu.com/questions/760871/network-settings-fail-for-ubuntu-xenial64-vagrant-box
- https://github.com/mitchellh/vagrant/issues/7155
- https://github.com/mitchellh/vagrant/pull/7318
Here's a TLDR of what you probably need to do:
1. Upgrade Vagrant to at least 1.9.2.
2. Install vagrant-vbguest.
vagrant plugin vagrant-vbguest
No comments:
Post a Comment