I've been working with Homestead for quite some time. A few days ago, I delete ubuntu because I had several problems of instability, I change to mint with the promise of being a little more stable and I miss this error .. Thinking that I had some problem in the distro, I returned to Ubuntu Mate. But the error is that it persists
I saw that someone proposed a similar problem on the stack but they did not go deeply into it. So I decided to open this.
I found several solutions, like entering the vagrant gui (which I can do) and changing the ports and some other configurations without results
The most suggested is to change the value of "config.vm.boot_timeout" in the VagrantFile to 600. But the truth is that my vagrantfile is not equal to the one proposed and this variable does not appear. So I do not know how to add it:
# -*- mode: ruby -*-
# vi: set ft=ruby :
require 'json'
require 'yaml'
VAGRANTFILE_API_VERSION ||= "2"
confDir = $confDir ||= File.expand_path("~/.homestead")
homesteadYamlPath = confDir + "/Homestead.yaml"
homesteadJsonPath = confDir + "/Homestead.json"
afterScriptPath = confDir + "/after.sh"
aliasesPath = confDir + "/aliases"
require File.expand_path(File.dirname(__FILE__) + '/scripts/homestead.rb')
Vagrant.require_version '>= 1.8.4'
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
if File.exist? aliasesPath then
config.vm.provision "file", source: aliasesPath, destination: "~/.bash_aliases"
end
if File.exist? homesteadYamlPath then
settings = YAML::load(File.read(homesteadYamlPath))
elsif File.exist? homesteadJsonPath then
settings = JSON.parse(File.read(homesteadJsonPath))
end
Homestead.configure(config, settings)
if File.exist? afterScriptPath then
config.vm.provision "shell", path: afterScriptPath, privileged: false
end
if defined? VagrantPlugins::HostsUpdater
config.hostsupdater.aliases = settings['sites'].map { |site| site['map'] }
end
end
Try to destroy it, recreate it and nothing. I would have to try an older version of vagrant. I do not remember what I had before.
vagrant version: 1.8.7 vbox version: 5.0.24
Any solution?