[ACCEPTED]-Bundle install not using rbenv local Ruby version-rbenv

Accepted answer

Score: 16

To add to this, in my case, I first had 3 to run rbenv rehash and then install the bundler gem, and 2 then re-run bundle install. Without all of those steps, it 1 kept the same old Ruby version.

Score: 3

You should be able to just run bundle install without 7 the --path. I believe --path allows you 6 to specify a different path than the one 5 in your system, but if you modified your 4 bash profile as you suggested, there is 3 no need for that.

Also, if you just changed 2 your ruby version for the local folder, you 1 should run a gem install bundler.

Source: stackoverflow.com

[ACCEPTED]-Bundle install not using rbenv local Ruby version-rbenv

I'm using rbenv, so why are there two Gem paths on my system? (OS X Lion)

Prepending `bundle exec` to your command may solve this rails

Using multiple Bundler versions

unable to install mysql2 Gem on Bigsur

Rails: Could not find minitest-4.7.5 in any of the sources

Using --no-rdoc and --no-ri with bundler

ERROR: Failed to build gem native extension - Error installing mysql2

bundle install error - ruby_dep-1.5.0 requires ruby version >= 2.2.5 but I have version 3.0.1p64

why is gem still outdated after bundle update

Can you have multiple versions of a gem in a Gemfile?