Reputation: 2466

Why won't bundler install JSON gem?

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.

Upvotes: 88

Answers (19)

Juice007

Reputation: 1062

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!

Upvotes: 41

PetrolHead

Reputation: 430

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

Upvotes: 5

Devin

Reputation: 149

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'.

Upvotes: 0

Rohini Choudhary

Reputation: 2473

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.

Upvotes: 35

Adam

Reputation: 464

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.

Upvotes: 9

anti-k

Reputation: 317

bundle update json. Helped to get through.

Upvotes: 7

davidmccoy

Reputation: 61

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

Upvotes: 2

iHS

Reputation: 5432

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

Upvotes: 0

Lucas

Reputation: 121

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.

Upvotes: 12

Koala7

Reputation: 1404

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

Upvotes: 0

Tim Kozak

Reputation: 4182

For OS X make sure you have coreutils

$ brew install coreutils
$ bundle

Upvotes: 3

PerseP

Reputation: 1197

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

Upvotes: 1

danvitoriano

Reputation: 1401

$ bundle update json
$ bundle install

Upvotes: 76

Haris Krajina

Reputation: 15276

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

xcode-select --install

Hope it helps.

Upvotes: 2

Ajeet Khan

Reputation: 9190

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

Upvotes: 20

Jameel Mohammed

Reputation: 2364

Run this command then everything will be ok

sudo apt-get install libgmp-dev

Upvotes: 49

Matthias

Reputation: 150

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.

Upvotes: 7

jearlu

Reputation: 550

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.

Upvotes: 2

Thomas

Reputation: 2466

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'

Upvotes: 68

Why won&#39;t bundler install JSON gem?

Answers (19)

Related Questions

Why won't bundler install JSON gem?