Hi everyone,
On vagrant up comand, using latest version of vagrant and fresh installation of Win 10.
My homestead file is attached, but basically is the default one with small changes, so it should not have any parsing issues.
I am using Laravel/Homestead.
Anyone with the same problem?
Homestead.txt
D:\Homestead>vagrant up
C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/psych.rb:377:in parse': (<unknown>): mapping values are not allowed in this context at line 2 column 3 (Psych::SyntaxError)
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/psych.rb:377:inparse_stream'
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/psych.rb:325:in parse'
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/psych.rb:252:inload'
from D:/Homestead/Vagrantfile:29:in block in <top (required)>'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/config/v2/loader.rb:37:inload'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/config/loader.rb:126:in block (2 levels) in load'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/config/loader.rb:119:ineach'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/config/loader.rb:119:in block in load'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/config/loader.rb:116:ineach'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/config/loader.rb:116:in load'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/vagrantfile.rb:29:ininitialize'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:793:in new'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:793:invagrantfile'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:178:in initialize'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/bin/vagrant:145:innew'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/bin/vagrant:145:in `
Sounds like either something in Vagrant is broken on your system (reinstall to fix it) or there is something syntactically wrong with your YAML configuration. Since you posted in txt it's hard to know.
It's also hard to see other things that can help debug because you didn't fill out the issue template.
yes, I had the same problem, it was a involuntary changes in my .yaml file, I fixed checking this file with the example-file, and I found the different
Most helpful comment
Sounds like either something in Vagrant is broken on your system (reinstall to fix it) or there is something syntactically wrong with your YAML configuration. Since you posted in
txtit's hard to know.It's also hard to see other things that can help debug because you didn't fill out the issue template.