Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1044405
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T15:49:26+00:00 2026-05-16T15:49:26+00:00

I am using rvm, doing the following: rvm install ree <— (Ruby Enterprise Edition),

  • 0

I am using rvm, doing the following:

rvm install ree    <--- (Ruby Enterprise Edition), or this can be 1.8.7 or 1.9.2
rvm ree
rvm gemset create 'proj'
cd path/to/proj
bundle install

so Gemfile in that project says:

gem 'rails', '3.0.0'

and bundle install is super fast, reporting

Using rails (3.0.0) 

but after that when I type

$ rails -v
/Library/Ruby/Site/1.8/rubygems.rb:779:in `report_activate_error': Could not find RubyGem rails (>= 0) (Gem::LoadError)
    from /Library/Ruby/Site/1.8/rubygems.rb:214:in `activate'
    from /Library/Ruby/Site/1.8/rubygems.rb:1082:in `gem'
    from /usr/bin/rails:18

$ which rails
/usr/bin/rails

so bundle install doesn’t install the rails as a gem?
but if I type script/rails -v it shows it is 3.0.0

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T15:49:27+00:00Added an answer on May 16, 2026 at 3:49 pm

    This is correct. bundle install won’t install Rails as a gem in the conventional sense. Now to explain why.

    When Bundler runs an install, it will install the gems a directory: ~/.bundle/<type-of-ruby>/<version>/gems. This is different to the normal way of installing them to a system path. When a gem is installed at a system path, the executable is made available because that directory is within the load path. Now this is a bad thing, because you can only have one executable per gem. Have you got SomeGem v2 installed but want to use the generator from SomeGem v1? Too bad.

    Bundler solves this problem by installing them into the afore-mentioned location and only requiring specific versions of the gems it needs (specified inside of Gemfile. By running simply rails, you’re trying to run the system executable (as in one provided by doing gem install rails) rather than the Bundler one (provided by doing bundle install for a Rails project).

    To run the one that Bundler installs you must run it like this bundle exec rails within a directory that contains a Gemfile that specifies any version of Rails. Bundler will load a specific version of Rails and you should now be able to run them side-by-side with the only tradeoff being the bundle exec prefix to commands.

    Personally I’ve aliased this to be and two characters before some commands is a worthwhile tradeoff to avoiding The Seventh Circle of Gem Conflict Hell in my opinion.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am trying to install ruby using rvm. I get the following error on
I am using rvm, ruby 1.9.3, link-grammar (sudo apt-get install link-grammar), and pkg-config. I
I tried to install Ruby 1.9.3 using RVM. It seems that it installed without
Hi I'm trying to upgrade my ruby 1.9.2 to 1.9.3 using RVM. This is
I have installed rvm (mutiuser option) and ruby using rvm install on my test
I tried installing ruby 1.9.3 on Snow Leopard using: rvm install 1.9.3 --with-gcc=clang After
When trying to install gems using rvm i get this error $ rvm gem
I'm using Ubuntu 11.04, rvm and Heroku. When I'm doing this heroku logs --tail
I am trying to install ruby 1.9.2 from a ruby script using rvm which
I'm trying to install ruby using RVM in Cygwin, but I'm getting the error:

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.