I'm trying to install a new VM with VAPROBASH (https://github.com/fideloper/Vaprobash)
but the installation fails when mounting NFS shared folders
I'm using Mac OsX 10.9.2, Vagrant 1.6.2, VirtualBox 4.2.20
=> default: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o 'nolock,vers=3,udp,noatime' 192.168.22.1:'/Users/user/Sites/myfolder' /vagrant
Stdout from the command:
Stderr from the command:
stdin: is not a tty
mount.nfs: requested NFS version or transport protocol is not supported
Any help would be appreciated! Thanks! I need to start a project!
I´ve found the solution:
adding the line 127.0.0.1 localhost to the /etc/hosts file worked for me as well
I'm with vagrant 1.6.2 and vbox 4.3.10
https://github.com/mitchellh/vagrant/issues/1941#issuecomment-43098597
Related
Laravel/homestead version: 9.3.0
VirtualBox version: 6.0
Vagrant version: 2.2.6
i'm trying to use NFS with laravel/homestead per project setup. i used to have all projects within same homestead environment, but changed it to per projects yesterday.
All sites is working fine when NOT using nfs. (except from being really slow)
I've installed Vagrant WinNFSd.
the error is:
==> bpa: Exporting NFS shared folders...
==> bpa: Preparing to edit nfs mounting file.
[NFS] Status: halted
[NFS] Start: started
==> bpa: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp,actimeo=1,nolock 192.168.10.1:/D/SynologyDrive/Prosjekter/Privat/bpa /home/vagrant/code
Stdout from the command:
Stderr from the command:
mount.nfs: an incorrect mount option was specified
i've searched google and tried everything without luck.
the setup:
folders:
-
map: 'path\to\project'
to: /home/vagrant/code
type: "nfs"
I am trying to set up vagrant for kong. I have installed VirtualBox and vagrant. But when i run 'vgrant up' i encounter the below issue:
Bringing machine 'default' up with 'virtualbox' provider...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["list", "hostonlyifs"]
Stderr: VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
I have searched for this error with no much luck.
I am using centos 7.4 and the kernel version is 3.10.0-693.21.1.el7.x86_64.
I have downloaded the relevant gcc, devel and dkms. In short followed the link https://tecadmin.net/install-oracle-virtualbox-on-centos-redhat-and-fedora/
Any tip is appreciated.
Thanks
Dinah
This is most likely a problem with your VirtualBox install, not Vagrant. To confirm this, you should receive the same error when running: VBoxManage list vms
A common reason for this error are when /tmp is full or has the incorrect permissions.
To check if /tmp is full try df -h
To fix permissions on /tmp if they're incorrect, try sudo chmod ug-s /tmp && sudo rm -rf /tmp/.vbox*
Apparently we were trying this on a VM. And Vagrant tries to spin up another VM. So having a VM spun within a VM is causing the issue.
I've some trouble with mounting folder using Vagrant & Puphpet.
This is the error message (with --debug) :
/opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
INFO interface: error: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp 192.168.56.1:/var/www/vm /mnt/vagrant-vflsf_dz1yb40c5aje
Stdout from the command:
Stderr from the command:
mount.nfs: Connection timed out
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp 192.168.56.1:/var/www/vm /mnt/vagrant-vflsf_dz1yb40c5aje
Stdout from the command:
Stderr from the command:
mount.nfs: Connection timed out
INFO interface: Machine: error-exit ["Vagrant::Errors::NFSMountFailed", "The following SSH command responded with a non-zero exit status.\nVagrant assumes that this means the command failed!\n\nmount -o vers=3,udp 192.168.56.1:/var/www/vm /mnt/vagrant-vflsf_dz1yb40c5aje\n\nStdout from the command:\n\n\n\nStderr from the command:\n\nmount.nfs: Connection timed out\n"]
This is strange 'cause the IP pf the box is "192.168.56.102", not "192.168.56.1" and why "udp" ?
I've installed this package and plugin :
sudo apt-get install nfs-kernel-server
vagrant plugin install vagrant-bindfs
vagrant plugin repair
I'm on :
Vagrant 1.9.3
VirtualBox 5.0.32_Ubuntu r112930
Linux spectre 4.4.0-66-lowlatency #87-Ubuntu SMP PREEMPT Fri Mar 3 16:43:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
If I add --debug with Vagrant, the system ask me for root password, but, without the parameter, don't ask.
Any idea please ?
Thanks
Fabrice
For me the culprit is Cisco's AnyConnect VPN client.
If you disconnect everything will work fine (No more Mounting NFS shared folders hangs).
Hoping to be useful.
I'm trying to install the last laravel homestead.
After cloning the repo into ~/Homestead and launch vagrant up.
I have this error :
==> homestead-7: Mounting shared folders...
homestead-7: /vagrant => C:/Users/fboland/Homestead
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 vagrant /vagrant
The error output from the command was:
: No such file or directory
But the folder realy exists !
Any idea ?
Thanks
If you are using VirtualBox 5.1.16 (the latest at the time of writing this), you will have to downgrade to VirtualBox 5.1.14 as there is an issue with the version of Guest Additions in this release.
More information in this issue on GitHub: https://github.com/laravel/homestead/issues/510
Installing the vbguest plugin worked in my case with VirtualBox 5.2.6 and Vagrant 2.0.2:
vagrant plugin install vagrant-vbguest
I am using vagrant on windows 8.1 and when I am doing vagrant up I am getting this error
The error message states that it failed trying execute this command:
chown `id -u vagrant`:`id -g vagrant` /vagrant
So I accessed the host machine by ssh: and I tried to execute the same command and I get error
Here is some commands I tried to execute in /vagrant directory, I don't know if that will help.
Here is my vagrantFile that I am using.
Please any idea what I am doing wrong ?
/vagrant probably doesn't exist
Check for /home/projects
This line in your Vagrantfile sets that directory. ./projects is on the host, /home/projects is on the guest.
config.vm.synced_folder "./projects", "/home/projects", nfs: true