-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Vagrant - instalation error #104
Comments
I now believe this is a problem with both Vagrantfile and Vagrant itself. The vagrantfile is configured to use ruby 1.9.1, byt other packages require ruby 2.0 or higher. Configuring the file to download dependencies from readme: Console output, where errors apper: (executing gem1.9.1) ==> default: /srv/mapwarper /home/vagrant After ssh to the machine and executing "rails c" it informas that rails was not installed. |
Thanks for looking into it. Try changing bundle to "bundler" ? |
So it seems as if tins-1.12.0 is what's causing the issue. I think this may be required from i18n-tasks which has been newly added - if you comment out i18n-tasks in Gemfile what happens? |
Strangely changing "bundle" to "bundler" results in: ==> default: /srv/mapwarper /home/vagrant I changed it back to "bundle" but I still get the same errors. According to this: Then I deleted machine and run "vagrant up" one again. This time with "i18n-tasks" commented out and with "budle" and got: ==> default: file 'lib' not found |
After executing vagrant up virtual machine is created and duting that process following error apeers:
==> default: ERROR: Could not find a valid gem 'bundle' (>= 0) in any repository
==> default: ERROR: Possible alternatives: bundle
==> default: /srv/mapwarper /home/vagrant
==> default: sudo: bundle: command not found
==> default: CREATE EXTENSION
==> default: now migrating database. This may take a few minutes
==> default: sudo: bundle: command not found
==> default: /home/vagrant
I can ssh into the virtual machine, but rails in not installed on it - rails c and other commands are not recognized. Is the vagrantfile up to date?
Problem appers on Window 7 64 bit.
The text was updated successfully, but these errors were encountered: