Open lhgrubbs opened 10 years ago
This whole environment is new to me. Here is the status of the VM and init
Current machine states:
default poweroff (virtualbox)
The VM is powered off. To restart the VM, simply run vagrant up
leroygrubbsmbp:canvas-lms-dev-box LeRoy$ vagrant up
There were warnings and/or errors while loading your Vagrantfile
for the machine 'default'.
Your Vagrantfile was written for an earlier version of Vagrant, and while Vagrant does the best it can to remain backwards compatible, there are some cases where things have changed significantly enough to warrant a message. These messages are shown below.
Warnings:
config.vm.customize
calls are VirtualBox-specific. If you're
using any other provider, you'll have to use config.vm.provider in a
v2 configuration block.Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 3000 => 3000 (adapter 1)
default: 22 => 2222 (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 timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 4.2.0
default: VirtualBox Version: 4.3
==> default: Setting hostname...
==> default: Mounting shared folders...
default: /vagrant => /Volumes/scratch/rails/canvas-lms-dev-box
default: /tmp/vagrant-puppet-3/manifests => /Volumes/scratch/rails/canvas-lms-dev-box/puppet/manifests
default: /tmp/vagrant-puppet-3/modules-0 => /Volumes/scratch/rails/canvas-lms-dev-box/puppet/modules
==> default: Machine already provisioned. Run vagrant provision
or use the --provision
==> default: to force provisioning. Provisioners marked to run always will still run.
leroygrubbsmbp:canvas-lms-dev-box LeRoy$ vagrant ssh
There were warnings and/or errors while loading your Vagrantfile
Setup and ran "vagrant ssh", then "bundle exec rake db:initial_setup". System suggested running "sudo apt-get install ruby-bundler". Appears to be working. Now when running "bundle exec rake db:initial_setup" Getting error messages:
vagrant@canvas-lms-dev-box:/vagrant/canvas-lms$ bundle exec rake db:initial_setup /usr/lib/ruby/vendor_ruby/bundler/rubygems_ext.rb:8:in
require': no such file to load -- rubygems (LoadError) from /usr/lib/ruby/vendor_ruby/bundler/rubygems_ext.rb:8 from /usr/lib/ruby/vendor_ruby/bundler.rb:11:in
require' from /usr/lib/ruby/vendor_ruby/bundler.rb:11 from /usr/bin/bundle:4:in `require' from /usr/bin/bundle:4 vagrant@canvas-lms-dev-box:/vagrant/canvas-lms$Any Ideas would be appreciated.