Your Ruby version is 2.0.0, but your Gemfile specified 2.1.0

Question

When I try to bundle install I get the following message:

Your Ruby version is 2.0.0, but your Gemfile specified 2.1.0

In my Gemfile I have the following:

ruby '2.1.0'

And when I run ruby -v in the console I get:

ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin12.0]

What does Ruby 2.1.0p0 mean? What version should I have in my Gemfile and why does the error tell me I have Ruby version 2.0.0?

add `.rvmrc` with `rvm use 2.1.0 > /dev/null` in project dir. this swith ruby version. — Roman Kiselenko, Apr 13 '14 at 05:51
What does that do? I added a file in my proj dir called `.rvmrc` and put in it `rvm use 2.1.0 > /dev/null`. Unfortunately I still get the same message when I run bundle install: `Your Ruby version is 2.0.0, but your Gemfile specified 2.1.0` — stecd, Apr 13 '14 at 05:56
and run `gem install bundler` or `gem update bundler` this may fix your problem. — Roman Kiselenko, Apr 13 '14 at 06:03
the .rvmrc file is uneeded. The `gem update bundler` did the job. Thank you — stecd, Apr 13 '14 at 06:15
I updated the `Gemfile` then ran `Bundle install` and worked for me. — Ivan Carrasco Quiroz, Feb 05 '19 at 18:44
Kind of a brain fart on my part, but I got this error while running a `docker-compose build` because the Dockerfile started with an older version of Ruby than used in other places. — beyondtheteal, Feb 06 '19 at 03:09

score 110 · Accepted Answer · edited Apr 13 '17 at 23:52

110

Run

gem install bundler

or

gem update bundler

which may fix your problem.

For all new installed versions of Ruby you should update or install a new bundler.

edited Apr 13 '17 at 23:52

the Tin Man

158,662
42
215
303

answered Apr 13 '14 at 06:20

Roman Kiselenko

43,210
9
91
103

11

I'm running into the exact same issue, but this is not fixing it for me. Can you elaborate a bit more on why this would work? After installing bundler, I still get `Your Ruby version is 2.0.0, but your Gemfile specified 2.0.0-p645`. `rbenv` does not even _have_ 2.0.0. – Joost Jul 26 '15 at 22:59
7

ha. this even worked for my 2.0.0 vs 2.2.4 problem, although i got a ```Nothing to update``` message when updating bundler. ¯\_(ツ)_/¯ – manmal Mar 11 '16 at 11:36
Had the same problem, my gemfile specified 2.2.2 and I also had a .ruby-version file. `rvm info` also gave me 2.2.2 - gem update bundler fixed the error :) didn't have to mess with `rbenv`. – Adam Cooper Mar 17 '16 at 07:54
5

If you just installed that version, restarting your shell may help as well. – Courtney Pattison Mar 18 '17 at 17:58
also received the `Nothing to update` message, but `gem update bundler` worked immediately. – Mark Peterson Mar 29 '18 at 01:26
same here, received Nothing to Update message but it works somehow. not sure why... – Realizt30 Apr 05 '20 at 06:24

score 15 · Answer 2 · answered May 14 '14 at 15:30

15

In the top-level directory of your project, create a file named .ruby-version containing (wait for it...)

2.1.0

That apparently is the cross-{rbenv,rvm} way of spec'ing the version now.

answered May 14 '14 at 15:30

Clay Bridges

11,602
10
68
118

score 14 · Answer 3 · answered Mar 07 '18 at 14:07

14

For me, none of the answers helped. I fixed it closing and opening again the terminal.

answered Mar 07 '18 at 14:07

Juan José Ramírez

639
6
10

This worked for me as well, however keep in mind that this is because the terminal window we were in had some sort of different source loaded. Our default source happened to work. – KazaJhodo Aug 28 '18 at 15:04

score 13 · Answer 4 · edited Apr 13 '17 at 23:53

13

If you get this in a Rails project, and you recently upgraded your Ruby version you might have spring still running with the old version of Ruby.

./bin/spring stop

will fix this.

edited Apr 13 '17 at 23:53

the Tin Man

158,662
42
215
303

answered Mar 04 '15 at 19:42

Myers Carpenter

939
1
9
12

score 7 · Answer 5 · answered Jan 24 '19 at 15:51

7

None of the other suggestions was working for me. On the server, I had to do:

rvm --default use [correct version number]

answered Jan 24 '19 at 15:51

Loren

3,476
3
23
15

score 4 · Answer 6 · answered Oct 01 '18 at 13:03

4

brew cleanup ruby worked for me as I use HomeBrew to install Ruby.

I recently updated Ruby through HomeBrew but HomeBrew did not remove the older version. brew cleanup ruby will delete the older version of Ruby.

answered Oct 01 '18 at 13:03

ethicalhack3r

1,062
3
15
16

score 4 · Answer 7 · answered Feb 12 '20 at 14:05

the main reason for this problem is your machine and gemfile using a different ruby version

so there is multiple problems and solutions for this issue you can try the below solutions one by one

1- make sure your machine install and use the same version of your gemfile if your machine not using the same one try to install this version using rvm

$ rvm install ruby_version_you_want

make sure the version installed success by using this command

$ rvm list

and if the new version doesn't set as a default you can set it using this command

$ rvm --default use ruby_version_you_want

you can check the current ruby version

 $ rvm current 
 $ ruby -v

2- if you have the same issue check your bundler

  $ gem install bundler
    or
  $ gem update bundler

3- in some cases spring still using the old version so you need to stop it

$ ./bin/spring stop

4- another case you can type

$ gem pristine --all

and try to install bundle again

5- also in some cases after install the updated ruby version you just need to restart your terminal.

6- another solution but I didn't recommend it the top-level directory of your project, create a file named .ruby-version containing your active running ruby version

7- if you still have this problem try to remove ruby and install the updated version only

 $ aptitude purge ruby

score 3 · Answer 8 · edited Apr 13 '17 at 23:56

3

If you are using Capistrano you should also check your deploy.rb file for the set :rbenv_ruby configuration.

edited Apr 13 '17 at 23:56

the Tin Man

158,662
42
215
303

answered Nov 26 '14 at 15:50

Darme

6,984
5
37
52

or this could be in the Capfile – Jerome Apr 07 '17 at 11:20

score 3 · Answer 9 · answered Apr 21 '17 at 01:45

I got this after upgrading with ruby-install. Fixed this with:

gem install bundler

followed by:

$HOME/.rubies/ruby-2.4.1/bin/bundle

It shouldn't be necessary to specify the path as which bundle indicates it's already using this path. But it gives the version error if running bundle without the path. I don't know why?

score 3 · Answer 10 · answered Jul 26 '18 at 08:36

3

Thanks for the info about installing / updating bundler but it didn't work for me. I had to do rbenv rehash

answered Jul 26 '18 at 08:36

MarkP

171
1
5

This, preceded by Thiemo's answer, worked for me on Ubuntu. – eddz Oct 05 '20 at 00:35

score 2 · Answer 11 · answered Sep 09 '17 at 20:59

2

If you are using rbenv to manage your ruby environments you can run rbenv local 2.1.0 within your project directory to set the version of ruby your gemfile asks for.

answered Sep 09 '17 at 20:59

Tim

21
2

score 2 · Answer 12 · answered Jan 22 '19 at 11:16

2

NONE of the above answers worked for me, but

$ gem pristine --all

did the trick for me

buona fortuna

answered Jan 22 '19 at 11:16

Salomanuel

897
10
22

score 2 · Answer 13 · answered Jan 29 '20 at 21:22

I struggled with something very similar, just different versions. I finally fixed it by going to RubyGems and placing the latest version of bundler in my gemfile, which currently is:

gem 'bundler', '~> 2.1', '>= 2.1.4'

There was still an issue, but after that, I ran:

gem update --system

And it resolved the mixed-up versions of Ruby in the rails project folder. You may have to restart the terminal before you do this. Also, I commented out the bundler gem file, it appears the gem update --system command is what really resolved it.

I got it from here:

score 1 · Answer 14 · edited Apr 13 '17 at 23:54

1

For more advanced projects .versions.conf is supported, where more than the Ruby version can be specified.

Generating .versions.conf:

rvm --create --versions-conf use 1.9.3@my_app

Example .versions.conf:

ruby=jruby-1.6.8
ruby-gemset=my_app
env-JRUBY_OPTS=--1.9

edited Apr 13 '17 at 23:54

the Tin Man

158,662
42
215
303

answered Sep 09 '15 at 03:50

user5315333

11
1

score 1 · Answer 15 · answered Aug 05 '17 at 21:08

Make sure your server configuration points to the correct ruby installation.

I had already updated my Ruby version in the .ruby-version file and that didn't fix it. ruby -v also showed the correct version, but I had forgotten to update my server config.

For example, with rbenv, NGINX, and Pushion Passenger I had in my NGINX server block:
passenger_ruby /Users/myusername/.rbenv/versions/2.3.1/bin/ruby;

And I needed to change to...
passenger_ruby /Users/myusername/.rbenv/versions/2.3.3/bin/ruby;

Then restarted NGINX and it worked.

score 1 · Answer 16 · answered Dec 17 '18 at 08:12

This could happen when you install new version of ruby and update .ruby-version and Gemfile to the new version without doing install all the gems for new version of ruby first. So do the

$ bundle install

and you might as well need to source .profile or restart your shell.

score 1 · Answer 17 · answered Jul 26 '20 at 09:49

1

If you are using rbenv just run

rbenv local 2.0.0

Then

bundle install

answered Jul 26 '20 at 09:49

Babatunde Mustapha

2,131
20
21

score 1 · Answer 18 · answered Oct 10 '20 at 11:07

1

I opened Gemfile and replaced 2.7.1 with my own version of ruby 2.7.0 Everything is okay right now.

answered Oct 10 '20 at 11:07

Oğuzhan Filiz

104
7

score 1 · Answer 19 · edited Mar 08 '22 at 10:13

Had the same problem and I'm working with rbenv

Those are the steps that helped me fix my problem:

First in terminal, type which bundle. For me this gave: /usr/local/bin/bundle
Again in terminal try which ruby. In my case this gave: /Users/Mahmoud/.rbenv/shims/ruby

The problem here thus is that bundle isn't using the same ruby version from rbenv. So the path needs fixing. In other words I need to tell my terminal to use the rbenv version of bundle when I use bundle install.

So step 3: For me I personally already had the path set in ~/.bash_profile:

export PATH="$HOME/.rbenv/shims:$PATH"
eval "$(rbenv init -)"

but apparently this was not enough as I was using zsh. Had to add those same 2 lines to ~/.zshrc as well.

Restart terminal

Now bundle install is working as expected and which bundle gives:

/Users/Mahmoud/.rbenv/shims/bundle

indicating that the problem was just that bundle was using the wrong ruby.

So if you have this problem, just make sure ~/.bash_profile and ~/.zshrc have the correct path by adding the 2 lines indicated above. If this didnt work take a deep dive into paths to make sure that before starting which bundle gives the equivalent of:

/Users/Mahmoud/.rbenv/shims/bundle

score 0 · Answer 20 · answered May 13 '19 at 12:54

0

Had the same error. Doing the following fixed it. I was using ruby 2.5.5 and rbenv. Upgraded from 2.5.1.

rbenv rehash
gem uninstall bundler
gem install bundler
gem install bundler:1.17.3 (my app needed specific bundler -v 1.17.3)
gem install rails

answered May 13 '19 at 12:54

Andrius Svylas

11
1
2

score 0 · Answer 21 · answered Aug 12 '20 at 03:51

0

I solved this problem by updating my ruby version to ruby '2.4.0' Then bundle install

answered Aug 12 '20 at 03:51

nourza

2,215
2
16
42

score 0 · Answer 22 · answered Nov 23 '20 at 12:40

0

Simply closing the terminal I was working on and opening a new one worked for me. Sometimes, updates are not effected immediately until a session is closed. I have found this as the case with many rails errors I faced.

answered Nov 23 '20 at 12:40

Oluebube Princess Egbuna

91
1
3

score 0 · Answer 23 · answered Jul 26 '22 at 18:04

0

I clean and install with that:

sudo gem pristine --all

and install again:

bundle install

answered Jul 26 '22 at 18:04

Idan

3,604
1
28
33

score -3 · Answer 24 · answered May 22 '18 at 09:13

-3

I face the error msg

Your Ruby version is 2.5.1, but your Gemfile specified 2.3.0

and solved by the following steps:

open Gemfile which located at your directory.
change ruby '2.3.0' to ruby '2.5.1' and save the Gemfile
go back to items and run bundle update.

the issue is perfectly solved.

answered May 22 '18 at 09:13

Jerome Li

1,492
14
20

1

This is not a solution. This is a workaround. What if the code requires version `2.3.0` compulsorily. – JaydeepW Aug 06 '18 at 05:31
It is a terrible idea to just change the project required ruby version. Many things can stop working. The developer needs to use the project ruby version. – Leticia Esperon Aug 07 '18 at 17:55

Your Ruby version is 2.0.0, but your Gemfile specified 2.1.0

24 Answers24

Linked

Related