I was running 2.0.1 fine - upgraded to 2.0.4, broke it.
4 thoughts on “Upgraded Vagrant, broke it.”
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Importing base box ‘jadesystems/rails-5-2’…
==> default: Matching MAC address for NAT networking…
==> default: Checking if box ‘jadesystems/rails-5-2’ is up to date…
==> default: Setting the name of the VM: Omlya_default_1525140538176_11238
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
==> default: Forwarding ports…
default: 3000 (guest) => 3000 (host) (adapter 1)
default: 4000 (guest) => 4000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running ‘pre-boot’ VM customizations…
==> default: Booting VM…
==> default: Waiting for machine to boot. This may take a few minutes…
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection reset. Retrying…
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest…
==> default: Forcing shutdown of VM…
==> default: Destroying VM and associated drives…
C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/win32-file-security-1.0.10/lib/win32/file/security.rb:383:in `set_permissions’: Filesystem does not implement ACL support (ArgumentError)
from C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/vagrant-2.0.4/plugins/communicators/ssh/communicator.rb:200:in `ready?’
from C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/vagrant-2.0.4/plugins/communicators/ssh/communicator.rb:85:in `block in wait_for_ready’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:93:in `block in timeout’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in `block in catch’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in `catch’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in `catch’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:108:in `timeout’
from C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/vagrant-2.0.4/plugins/communicators/ssh/communicator.rb:62:in `wait_for_ready’
from C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/vagrant-2.0.4/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in `block in call’
# All Vagrant configuration is done below. The “2” in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don’t change it unless you know what
# you’re doing.
Vagrant.configure(“2”) do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://vagrantcloud.com/search.
# config.vm.box = “base”
config.vm.box = “jadesystems/rails-5-2”
config.vm.post_up_message = “Vagrant is Up”
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing “localhost:8080” will access port 80 on the guest machine.
# NOTE: This will enable public access to the opened port
# config.vm.network “forwarded_port”, guest: 80, host: 8080
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine and only allow access
# via 127.0.0.1 to disable public access
# config.vm.network “forwarded_port”, guest: 80, host: 8080, host_ip: “127.0.0.1”
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network “private_network”, ip: “192.168.33.10”
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network “public_network”
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder “../data”, “/vagrant_data”
# begin
# config.vm.synced_folder “C:/Users/User/Dropbox/My Work/Vagrant/Omlya”, “/omlya”
# rescue
#puts “Looks like we’re on the ASUS laptop”
# end
# begin
# config.vm.synced_folder “M:/data/Dropbox/My Work/Vagrant/Omlya”, “/omlya”
# rescue
# puts “Looks like we’re on the HP Elitebook 8440p laptop”
# end
# config.vm.synced_folder “.”, “/vagrant”, disabled: true
# just use the default!
# time in seconds for boot timeout – default is 300
# config.vm.boot_timeout=1000
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider “virtualbox” do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# # Customize the amount of memory on the VM:
# vb.memory = “1024”
# end
#
# View the documentation for the provider you are using for more
# information on available options.
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision “shell”, inline: <<-SHELL
# apt-get update
# apt-get install -y apache2
# SHELL
end
See, I have an ASUS G75V I use at home and an HP Elitebook 8440p I want to take traveling with me and work on rails stuff on the road.
The ASUS was working on older Vagrant and the HP not on new Vagrant but when I updated Vagrant on the ASUS it also stopped working.
That means it’s a software issue and should be resolved soon.
Notice, and this is typical of software, that the TROUBLE is the stupid communications crap at the end and the actual BIG thing, the VM itself, is fine.
I call situations like ‘being obstructed by a pebble’ meaning you’ve blasted a huge path through the mountain but there’s this ONE PEBBLE still there, and you can’t pass until it’s removed….
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Importing base box ‘jadesystems/rails-5-2’…
==> default: Matching MAC address for NAT networking…
==> default: Checking if box ‘jadesystems/rails-5-2’ is up to date…
==> default: Setting the name of the VM: Omlya_default_1525140538176_11238
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
==> default: Forwarding ports…
default: 3000 (guest) => 3000 (host) (adapter 1)
default: 4000 (guest) => 4000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running ‘pre-boot’ VM customizations…
==> default: Booting VM…
==> default: Waiting for machine to boot. This may take a few minutes…
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection reset. Retrying…
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest…
==> default: Forcing shutdown of VM…
==> default: Destroying VM and associated drives…
C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/win32-file-security-1.0.10/lib/win32/file/security.rb:383:in `set_permissions’: Filesystem does not implement ACL support (ArgumentError)
from C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/vagrant-2.0.4/plugins/communicators/ssh/communicator.rb:200:in `ready?’
from C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/vagrant-2.0.4/plugins/communicators/ssh/communicator.rb:85:in `block in wait_for_ready’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:93:in `block in timeout’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in `block in catch’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in `catch’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in `catch’
from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:108:in `timeout’
from C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/vagrant-2.0.4/plugins/communicators/ssh/communicator.rb:62:in `wait_for_ready’
from C:/HashiCorp/Vagrant/embedded/gems/2.0.4/gems/vagrant-2.0.4/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in `block in call’
Any ideas?
Here’s the actual vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The “2” in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don’t change it unless you know what
# you’re doing.
Vagrant.configure(“2”) do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://vagrantcloud.com/search.
# config.vm.box = “base”
config.vm.box = “jadesystems/rails-5-2”
config.vm.post_up_message = “Vagrant is Up”
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing “localhost:8080” will access port 80 on the guest machine.
# NOTE: This will enable public access to the opened port
# config.vm.network “forwarded_port”, guest: 80, host: 8080
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine and only allow access
# via 127.0.0.1 to disable public access
# config.vm.network “forwarded_port”, guest: 80, host: 8080, host_ip: “127.0.0.1”
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network “private_network”, ip: “192.168.33.10”
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network “public_network”
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder “../data”, “/vagrant_data”
# begin
# config.vm.synced_folder “C:/Users/User/Dropbox/My Work/Vagrant/Omlya”, “/omlya”
# rescue
#puts “Looks like we’re on the ASUS laptop”
# end
# begin
# config.vm.synced_folder “M:/data/Dropbox/My Work/Vagrant/Omlya”, “/omlya”
# rescue
# puts “Looks like we’re on the HP Elitebook 8440p laptop”
# end
# config.vm.synced_folder “.”, “/vagrant”, disabled: true
# just use the default!
# time in seconds for boot timeout – default is 300
# config.vm.boot_timeout=1000
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider “virtualbox” do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# # Customize the amount of memory on the VM:
# vb.memory = “1024”
# end
#
# View the documentation for the provider you are using for more
# information on available options.
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision “shell”, inline: <<-SHELL # apt-get update # apt-get install -y apache2 # SHELL end
I’m actually feeling better about this.
See, I have an ASUS G75V I use at home and an HP Elitebook 8440p I want to take traveling with me and work on rails stuff on the road.
The ASUS was working on older Vagrant and the HP not on new Vagrant but when I updated Vagrant on the ASUS it also stopped working.
That means it’s a software issue and should be resolved soon.
Notice, and this is typical of software, that the TROUBLE is the stupid communications crap at the end and the actual BIG thing, the VM itself, is fine.
I call situations like ‘being obstructed by a pebble’ meaning you’ve blasted a huge path through the mountain but there’s this ONE PEBBLE still there, and you can’t pass until it’s removed….