Why won't bundler install JSON gem?

Question

I get the following error when attempting to run cap production deploy.

DEBUG [dc362284] Bundler::GemNotFound: Could not find json-1.8.1.gem for installation DEBUG [dc362284] An error occurred while installing json (1.8.1), and Bundler cannot continue. DEBUG [dc362284] Make sure that `gem install json -v '1.8.1'` succeeds before bundling.

It may be important to note that this deployment was working, than I upgraded to Ruby 2.1.0 to remove an encoding error. I upgraded locally which worked fine. I ran rvm install 2.1.0 and rvm use 2.1.0 then changed my .ruby-version file to reflect this Ruby upgrade.

The bundle install command works locally, but produces the same above error when I ssh onto the destination server and run this command.

If I run gem list I can see this in the list of gems.

... jquery-rails (3.0.4) json (1.8.1) less (2.3.2) ...

If I try the recommended solution gem install json -v '1.8.1' Locally and on the destination server I get the following output:

Building native extensions. This could take a while... Successfully installed json-1.8.1 Parsing documentation for json-1.8.1 Done installing documentation for json after 0 seconds 1 gem installed

So it appears the gem is installed, right? Why is this happening? How can I solve this? Any help would be greatly appreciated.

I have gem json, '1.8.1' in my gemfile already unfortunately — Thomas
– Thomas, Commented Jan 13, 2014 at 15:38
bundle show json give /Users/ME/.rvm/rubies/ruby-2.1.0/lib/ruby/gems/2.1.0/gems/json-1.8.1 — Thomas
– Thomas, Commented Jan 13, 2014 at 15:38

danvitoriano · Accepted Answer · 2016-04-13 19:23:53Z

76

$ bundle update json $ bundle install

answered Apr 13, 2016 at 19:23

danvitoriano

1,49113 silver badges13 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

DMe Over a year ago

This did it for me on Ruby 2.4.0!

Aleksey Deryagin Over a year ago

Works for rbenv ruby 2.4.1 too (debian / ubuntu)

Robert_T_Taylor Over a year ago

This worked for me as well. Ruby 2.4.0 High Sierra. Thank you!

fatihturan Over a year ago

Worked for me too under Ruby version 2.4.2p198. Thanks.

Scott Lawrence Over a year ago

I upvoted this answer because it worked for me while the accepted answer did not. Like @Robert_T_Taylor, I ran this on macOS High Sierra.

Thomas · Accepted Answer · 2014-01-13 15:41:50Z

68

So after a half day on this and almost immediately after posting my question I found the answer. Bundler 1.5.0 has a bug where it doesn't recognize default gems as referenced here

The solution was to update to bundler 1.5.1 using gem install bundler -v '= 1.5.1'

answered Jan 13, 2014 at 15:41

Thomas

2,4763 gold badges24 silver badges38 bronze badges

6 Comments

Jason Denney Over a year ago

Had the same issue even after updating bundler, doing a gem install json -v '1.8.1' after updating fixed the error message for me.

Obie Over a year ago

gem install json -v '1.8.1' followed by bundle package did the trick for me

Snowcrash Over a year ago

Isn't bundler supposed to install these gems for you? I don't understand why you have to install the gems manually. bundler.io/rationale.html I'm using Bundler version 1.7.11

Pramod Shinde Over a year ago

This did not worked for me, sudo apt-get install libgmp3-dev worked , found solution github.com/flori/json/issues/253

Catfish Over a year ago

I'm using bundler version 1.14.6 and also getting this error

|

Jameel Mohammed · Accepted Answer · 2015-12-12 16:04:54Z

49

Run this command then everything will be ok

sudo apt-get install libgmp-dev

answered Dec 12, 2015 at 16:04

Jameel Mohammed

2,37421 silver badges33 bronze badges

Comments

Iulian Onofrei · Accepted Answer · 2020-07-07 13:14:23Z

if you are in MacOS Sierra and your ruby version is 2.4.0.The ruby version is not compatible with json 1.8.3.

You can try add this line in your Gemfile:

gem 'json', github: 'flori/json', branch: 'v1.8'

This works for me!

Rohini Choudhary · Accepted Answer · 2017-04-14 12:21:19Z

35

To solve this problem, simply run:

bundle update

It will update the version of your bundler. Then run:

bundle install

Your problem will get solve. Solution is well explained here.

edited Apr 14, 2017 at 12:21

answered Apr 13, 2017 at 9:38

Rohini Choudhary

2,4832 gold badges23 silver badges31 bronze badges

2 Comments

twk Over a year ago

+1 Really helpful and got me unstuck. After bundle update, the install worked great. Thank you for the clean solution.

eebbesen Over a year ago

bundle update will update all your gems. gem update bundler will update bundler.

Ajeet Khan · Accepted Answer · 2016-04-06 19:11:55Z

20

I found the solution here. There is a problem with json version 1.8.1 and ruby 2.2.3, so install json 1.8.3 version.

gem install json -v1.8.3

answered Apr 6, 2016 at 19:11

Ajeet Khan

9,2308 gold badges46 silver badges66 bronze badges

2 Comments

fuzzygroup Over a year ago

This worked fantastically for me on OSX, Ubuntu across multiple bad versions of the json gem. In one case I had to delete the lock file and rebuild from scratch: git rm Gemfile.lock bundle install

alexventuraio Over a year ago

Worked fine, first of all I delete the Gemfile.lock and then just run bundle install and that's it.

Lucas · Accepted Answer · 2016-08-10 00:54:14Z

You should try

$ sudo gem install json -v '1.8.2'

in my case (Ubuntu 14.04) that didn't work directly and I had to do this:

$ sudo apt-get install ruby-dev

and then I could install the gem and continue. Had one more problem that was fixed by:

$ sudo apt-get install libsqlite3-dev

Hoping helps.

Philip Kirkbride · Accepted Answer · 2017-03-20 13:38:51Z

9

If the recommended answer didn't help because you are already using a newer version of bundler. Try the solution that worked for me.

Delete everything inside your vendor folder. Add a line to your gemfile

gem 'json', '1.8.0'

Then run - bundle update json.

It seems to be an issue with 1.8.1 so going back to 1.8.0 did the trick for me.

edited Mar 20, 2017 at 13:38

Philip Kirkbride

23.1k39 gold badges134 silver badges238 bronze badges

answered Nov 4, 2014 at 21:20

Adam

4641 gold badge4 silver badges13 bronze badges

3 Comments

Loubot Over a year ago

Worked when upgrading from ruby 2.0.0 to 2.2.4.

Joffrey Baratheon Over a year ago

No need to delete everything. "bundle update json" sufficed.

etagwerker Over a year ago

Using gem 'json', '1.8.6' worked for me. You might want to try that.

Matthias · Accepted Answer · 2014-04-22 12:08:51Z

I ran into this error while trying to get a project to run on my local dev box (OSX 10.6), using Sinatra and Postgresql (through activerecord), running on an rvm'd ruby 2.1. I found my answer here: https://github.com/wayneeseguin/rvm/issues/2511

My exact problem (after the first block of log entries):

I also get an error when trying to build native extensions for gems

The answer:

rvm reinstall 2.1.0 --disable-binary

The explanation:

OSX does not have a package manager so all libraries have to be installed manually by user, this makes it virtually impossible to link the binary dynamically, and as you can see there are problems with the (pseudo)statically linked binary.

For the sake of completeness, I had first forgotten to update rvm (rvm get head), which yielded some other errors, but still needed the --disable-binary flag once I had done so.

Get the following error with your solution: "Version '2.1.0' is ambiguous. Cannot select Ruby implementation/version, please be more specific. Cannot reinstall unknown package ''"
You might not have ruby 2.1.0, or more than one version installed through rvm. Run rvm list, and you'll see what is your current version. Use the full string (e.g. ruby-2.0.0-p451) instead of the 2.1.0 mentioned above.

Peter DeWeese · Accepted Answer · 2017-03-01 22:33:19Z

7

bundle update json. Helped to get through.

edited Mar 1, 2017 at 22:33

Peter DeWeese

18.4k8 gold badges83 silver badges104 bronze badges

answered Jul 31, 2016 at 17:21

anti-k

3172 silver badges13 bronze badges

1 Comment

Simon Liu Over a year ago

Successfully installed json 1.8.6 (was 1.8.3)

PetrolHead · Accepted Answer · 2018-05-03 04:50:14Z

When I tried to install the json gem using gem install json separate from just using bundle install I got ERROR: Failed to build gem native extension., looking that up I found using

 apt-get install ruby-dev

did the trick

Tim Kozak · Accepted Answer · 2016-06-14 07:13:14Z

3

For OS X make sure you have coreutils

$ brew install coreutils $ bundle

answered Jun 14, 2016 at 7:13

Tim Kozak

4,22244 silver badges44 bronze badges

1 Comment

Paul Verschoor Over a year ago

Although I got a warning "Warning: coreutils 8.32 is already installed and up-to-date", this did the trick.

jearlu · Accepted Answer · 2014-02-07 19:59:22Z

This appears to be a bug in Bundler not recognizing the default gems installed along with ruby 2.x. I still experienced the problem even with the latest version of bundler (1.5.3).

One solution is to simply delete json-1.8.1.gemspec from the default gemspec directory.

rm ~/.rubies/ruby-2.1.0/lib/ruby/gems/2.1.0/specifications/default/json-1.8.1.gemspec

After doing this, bundler should have no problem locating the gem. Note that I am using chruby. If you're using some other ruby manager, you'll have to update your path accordingly.

yup, it's simple to solve a problem with json bundle. Thank you

Haris Krajina · Accepted Answer · 2016-04-12 11:23:30Z

I was missing C headers solution was to download it for Xcode, this is the best way.

xcode-select --install

Hope it helps.

davidmccoy · Accepted Answer · 2016-11-11 15:26:53Z

Bundle was failing to install json -v '1.8.1' and deleting my Gemfile.lock and running bundle again solved this issue for me.

PerseP · Accepted Answer · 2016-05-02 13:09:05Z

I installed the latest version of json:

gem install json

Then deleted the line json(1.8.1) from the Gemfile.lock and did a

bundle install

And then the Gemfile.lock file uses json(1.8.3) without erros

Just running a bundle update solved this issue for me... in other words using a newer JSON gem build.

Koala7 · Accepted Answer · 2016-07-11 19:14:10Z

0

Switch ruby version from 1.9 to 2.2 with rvm did the job for me

answered Jul 11, 2016 at 19:14

Koala7

1,4348 gold badges43 silver badges91 bronze badges

Comments

iHS · Accepted Answer · 2016-09-06 17:35:01Z

For me, some of the answers mentioned earlier were helpful from understanding point of view, but those didn't solve my problem.

So this is what I did to solve issue.

Modified gemfile.lock to update json (2.0.2) (Earlier, it was 1.8.3)
Check the Bundler version installed (Bundler -v command). I had version 1.12.5 installed
Install bundler version 1.11.2 (using gem install bundler -v '1.11.2')
Then run bundle install

Devin · Accepted Answer · 2017-07-28 15:03:20Z

For macOS Sierra:

I ran into this error When i used bundler(v1.15.3) in Rails(v4.2) project. The solution for me is gem uninstall bundler -v '1.15.3' and gem install bundler -v '1.14.6'.

Collectives™ on Stack Overflow

Why won't bundler install JSON gem?

19 Answers 19

5 Comments

6 Comments

Comments

Comments

2 Comments

2 Comments

Comments

3 Comments

2 Comments

1 Comment

Comments

1 Comment

1 Comment

Comments

Comments

1 Comment

Comments

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

19 Answers 19

5 Comments

6 Comments

Comments

Comments

2 Comments

2 Comments

Comments

3 Comments

2 Comments

1 Comment

Comments

1 Comment

1 Comment

Comments

Comments

1 Comment

Comments

Comments

Comments

Linked

Related