Firewall and guest

Question

On my system (OS X), I have an application running on Rails 3.1.0, ruby ​​1.8.7.

I installed Vagrant and configured it with virtual Ubuntu. I created a new ABC project from a virtual machine and installed ruby ​​1.9.3 and Rails 3.2.6 on the virtual machine.

Now, when I exit the Vagrant virtual machine and want to enter it again, from the ABC project directory, it is struggling with a conflict in the ABC Gemfile project:

~/.rvm/gems/ ruby-1.8.7-p358@global /gems/bundler-1.1.4/lib/bundler/spec_set.rb:90:in 'materialize': Could not find actionmailer-3.2.6 in any of the sources (Bundler::GemNotFound)

When I remove the Gemfile from the ABC project directory, I can use Vagrant without any problems.

Why is Vagrant checking the Gemfile project instead of just starting the virtual machine?

Has anyone experienced something like this before?

Answer 1

My current setup uses Vagrantfile separately from the rails directory.

I ended up with these settings after I started using the Puppet submission scripts, various bash scripts, the project documentation folder outside the rails, etc.

It makes sense to keep the rails application as clean as possible and not poison it with local development tool files (Vagrantfile).

The question remains valid. I'm not sure if this is suitable for reporting a problem on github ...

Answer 2

Vagrant uses the gemfile for plugins. See the documentation for plugins https://docs.vagrantup.com/v2/plugins/packaging.html .

So the tramp thinks your rail stones are plug-ins for stray and fail.