Open radumas opened 9 years ago
Vagrant is failing before it even gets to any of the open-transit-indicators code. nfsd not running -> You may want to look into that part a bit. Good luck!
Also, 'sudo service nfs-kernel-server start' should start it up.
@jbranigan
nfsd not running -> You may want to look into that part a bit. Good luck! Running
rpc.nfsd
prior tovagrant up
helped with this. But I still reach ==> default: Preparing to edit /etc/exports. Administrator privileges will be required... nfsd running exportfs: /home/rad/WorldBank/oti/open-transit-indicators does not support NFS export ==> default: Mounting NFS shared folders... The following SSH command responded with a non-zero exit status. etc....
Trying sudo service nfs-kernel-server start
within the oti folder produces
* Not starting NFS kernel daemon: no exports.
/etc/exports
contains
VAGRANT-BEGIN: 1000 ec75cd7a-089b-4036-8416-a00075b77091
"/home/rad/WorldBank/oti/open-transit-indicators" 192.168.4.2(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=4266025154)
VAGRANT-END: 1000 ec75cd7a-089b-4036-8416-a00075b77091
and after running vagrant destroy
the above lines vanish from /etc/exports
@radumas There's not much we can do in the way of Vagrant/OS support. I hope you can find a solution and run an OTI VM.
Not sure if this is an issue with the vagrant configuration of oti or is related to this: https://github.com/mitchellh/vagrant/issues/1941
I've installed virtualbox, nfs-common, nfs-server-kernel and the latest version of vagrant (1.7.2). When I try running
vagrant up
I get the following output.