i tried to install homestead but when i run
vagrant up
at the middle i got this error
My folder structure is
c:/Hashicorp/vagrant
and the homestead at
c:/Homestead
I've added this line on my vagrantfile inside homestead:
config.vm.synced_folder ".", "/vagrant"
but still no luck.
Virtual box version: 5.0
Vagrant version : 1.7.3
What should i do to make it running?
Related
I am trying to share a folder betwing my vagrant box and my host using this directive in Vagrantfile :
config.vm.synced_folder "./syncWithBox", "/var/www/html/"
The issue is that the /var/www/html/ folder is created during provisionning (installing apache2 server).
So when I vagrant up, there is an error because the /var/www folder does not exist before provisionning !
Is there a way to solve that ? How can I tell vagrant to perform folder sync after provionning ?
I saw a similar question here, but the answer is not exactly what I am looking for
This workaround works for me. I put the following command in an install.sh script and run it:
#!/bin/bash
vagrant plugin install vagrant-vbguest && vagrant up --no-provision
sed -i 's/#config.vm.synced_folder/config.vm.synced_folder/' Vagrantfile
vagrant halt && vagrant up --no-provision
vagrant provision
Install vbox addition with vagrant-vbguest plugin and Vagrant up the box without provisioning it
uncomment the synchronized folder directive using sed for example
stop the box and Vagrant it up without provisioning it : so the folders between host and guest are empty but synchronized
finally, provision the box
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'm unable to map my local project directory to Laravel's Homestead project directory. Inside of my homestead.yaml file I have:
folders:
- map: C:\Users\mdgre\Code
to: /home/vagrant/Code
When I run vagrant up I see the incorrect mapping taking place:
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => C:/Users/mdgre/.homestead
In addition when I ssh into the vagrant box no Code folder has been created at home/vagrant/Code.
Which version of homestead are you running? As of 5.0.0 there is no more ~/.homestead directory and shared folders are mounted using the Homestead.yaml config in the same directory as the Vagrantfile.
It doesn't work in the VirtualBox 5.1.16 version. You can update to the 5.1.18 version. It works in this version
Trying to spin-up a VM using vagrant and puppet 4.2. The puppent configuration in the Vagrantfile is:
config.vm.provision "puppet" do |puppet|
puppet.options = ['--verbose --debug']
puppet.environment_path = "../puppet/environments"
puppet.environment = "testenv"
end
as per Vagrant documentation (search for environments section)
After running vagrant up I get the following error message:
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:
puppet provisioner:
* The following settings shouldn't exist: environment, environment_path
Any thoughts?
I believe puppet 4 support was coming from 1.7.3 - you should upgrade vagrant to this version or even 1.7.4
issue was https://github.com/mitchellh/vagrant/pull/5601
and vagrant changelog
A VirtualBox machine with the name 'homestead' already exists. Please
use another name or delete the machine with the existing name, and try
again.
I've tried removing the machine from virtual box (deleting the files as well)
I've tried running vagrant destroy and homestead destroy as well.
I cant see to run homestead up or vagrant up. I keep getting the error i've stated above.
My VirtualBox\ VMs are empty.
➜ homestead homestead up Bringing machine 'default' up with
'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' is up to date... A VirtualBox machine with the name 'homestead' already exists. Please
use another name or delete the machine with the existing name, and try
again. ➜ homestead
Running vagrant global-status brings this:
5cd65e5 default virtualbox poweroff /Users/username/.composer/vendor/laravel/homestead
Im not sure how to fix this. Any help is greatly appreaciated.
You can manually delete the homestead in VirtualBox Gui. Open your VirtualBox Gui select homestead, click machines select poweroff.You can now delete homestead by selecting remove, and delete all related files, or go to Users\username\VirtualBox VMs and delete homestead folder as suggested by #Digitlimit.In your homestead directory, run
vagrant up
again