Bundler: You must use Bundler 2 or greater with this lockfile

Ruby on-RailsHerokuRuby on-Rails-5Heroku Cli

Ruby on-Rails Problem Overview


I'm working with heroku and every time I try to push my app this message shows out:

remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> Ruby app detected
remote: 
remote:  !
remote:  !     You must use Bundler 2 or greater with this lockfile.
remote:  !
remote: /tmp/d20181109-104-g861yi/bundler-1.15.2/gems/bundler-1.15.2/lib/bundler/lockfile_parser.rb:108:in `warn_for_outdated_bundler_version': You must use Bundler 2 or greater with this lockfile. (Bundler::LockfileError)
remote: 	from /tmp/d20181109-104-g861yi/bundler-1.15.2/gems/bundler-1.15.2/lib/bundler/lockfile_parser.rb:95:in `initialize'
remote: 	from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/helpers/bundler_wrapper.rb:130:in `new'
remote: 	from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/helpers/bundler_wrapper.rb:130:in `block in parse_gemfile_lock'
remote: 	from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
remote: 	from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
remote: 	from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/instrument.rb:17:in `block in instrument'
remote: 	from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/vendor/ruby/heroku-18/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
remote: 	from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/instrument.rb:16:in `instrument'
remote: 	from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/helpers/bundler_wrapper.rb:86:in `instrument'
remote:  !     Push rejected, failed to compile Ruby app.
remote: 
remote:  !     Push failed
remote: Verifying deploy...
remote: 
remote: !	Push rejected to my-proyect-1234.
remote: 

It says 'remote: ! You must use Bundler 2 or greater with this lockfile.'

> But my Bundler version is 2.0.0.pre.1

Don't know what to do, I tried uninstalling bundle and installing it again, I errased the Gemfile.lock and typing bundle again

Ruby on-Rails Solutions


Solution 1 - Ruby on-Rails

I had a similar experience.

Here's how I solved it

Display a list of all your local gems for the bundler gem

gem list bundler

N/B: The command above is for rbenv version manager, the one for rvm might be different

This will display the versions of the bundler gem installed locally

bundler (2.1.4, default: 1.17.2)

Note: Your versions might differ from the one here

if you don't have bundler version 2 installed locally, then run

gem install bundler

OR

gem install bundler -v 2.1.4

Note: Replace 2.1.4 with the version you want to install

if you have bundler version 2 already installed locally or just installed it, then you need to simply install an update for RubyGems Package Manager locally. To do this, run

gem update --system

And then finally run

bundle update --bundler

For Docker projects in Ruby on Rails

If you're experiencing this issue when trying to build your application using Docker, simply do this:

  1. Delete the Gemfile.lock file

  2. Please don't create it again by running bundle install.

  3. Run your docker build or docker-compose build command as appropriate to build your project.

This will re-create the Gemfile.lock file and setup the appropriate version of bundler necessary for your project in the Gemfile.lock file.

N/B: As a side note, you can also add this environment variable to your Dockerfile with the Bundler version defined.

ENV BUNDLER_VERSION=2.1.4

Solution 2 - Ruby on-Rails

A bit late to the party but I just ran into this today as well, and this solution avoids having to uninstall Bundler: just run

heroku buildpacks:set https://github.com/bundler/heroku-buildpack-bundler2

as per discussion on the Bundler issue here.

Solution 3 - Ruby on-Rails

> I had same issue on Local Machine(Development) as-

You must use Bundler 2 or greater with this lockfile.
The issue was with gemfile.lock because my local bundle version and project bundle version was not matching! Here is solution-

  1. I deleted gemfile.lock
  2. Run the command - bundle install
    That solved my problem, it is smooth! Hope will work for others!

Solution 4 - Ruby on-Rails

Even with bundler 2 on the system this error still happens when deploying an app with Ruby 2.6 since Ruby 2.6 ships with a default version of bundler.

If you are using Ruby 2.6 then upgrade to Ruby 2.6.1 to avoid this issue.

Solution 5 - Ruby on-Rails

simple gem update bundler did it for me.

Solution 6 - Ruby on-Rails

I resolved this issue by running gem uninstall bundler to remove 2.0.0.pre.1, renamed the Gemfile.lock file (to remove it from use) and then ran bundle install to reinstall the gemfiles. In my case, I already had access to the earlier bundler version installed by heroku (so when I ran gem uninstall, I was shown all versions available and chose to remove 2.0.0.pre.1).

Solution 7 - Ruby on-Rails

Yup, so generally uninstalling your version of bundler, removing the gemfile.lock, and finally running gem install bundler -v 1.15.2 (which is the version heroku is using) worked.

After that running git push heroku master worked!

Solution 8 - Ruby on-Rails

The Ruby 2.6.0 is not the case of this problem. The default version of Bundler incorrectly invoked when using bin stubs. For more details please refer the following link

Solution: Bundler 2 is available on the system and is the latest version, So it should be invoked instead of the default bundler version.

Update Rubygems

gem update --system

Update bundler

gem install bundler

Update Gemfile.lock in your project

bundler update --bundler

Solution 9 - Ruby on-Rails

For local system

gem install bundler:2.0.0.pre.1
bundle _2.0.0.pre.1_ install

Where "2.0.0.pre.1" is whatever version you need to bundle with.

Don't delete your Gemfile.lock for this, it's there for a reason.

Solution 10 - Ruby on-Rails

If you're using a docker image like FROM:ruby:2.X.X then you can do the following:

FROM ruby:2.6.2
... # omitted
COPY Gemfile /myapp/Gemfile
COPY Gemfile.lock /myapp/Gemfile.lock
RUN gem uninstall bundler
RUN gem install bundler -v 2.1.4
RUN bundle update --bundler
RUN bundle install
... # omitted

Solution 11 - Ruby on-Rails

Heroku does not use Bundler 2.0, but 1.15.2, as the tracelog hints.

As far as I am aware, the "workaround" is to create your own buildpack, or simple fork their own:

> Open lib/language_pack/ruby.rb in your editor, and change the following line: > > BUNDLER_VERSION = "1.11.2"

(README.md at https://github.com/heroku/heroku-buildpack-ruby)

Update: As of Ruby 2.6.1 and Bundler 2.0.1, Heroku now does support Bundler 2.0.1. https://devcenter.heroku.com/articles/bundler-version#known-upgrade-issues

This is not the case for Ruby 2.6.0, as this is incorrectly invoked from binstubs, as @Schneems has mentioned in the comment. He has kindly reported this as a Ruby Bug #15622

Solution 12 - Ruby on-Rails

For people who are not using Heroku:

I Tried everything and I was still receiving this error. even this link didn't help me: https://github.com/jekyll/jekyll/issues/7463

So this was my solution:

Push your code on GitHub. delete project folder create a new folder and pull your code bundle install That's it. bundler update --bundler was not helping me at the end and I didn't use it.

One more important thing: I updated my ruby version but I was getting this error because my RVM default version was an old version. even when you use rvm use VERSION_NUMBER -- default will not help because as soon as you log out from terminal the default version will change to the old one and you will have the same issue.

For this you can use this answer: https://stackoverflow.com/questions/7696633/how-to-set-default-ruby-version-with-rvm

or just uninstall old ruby version with rvm uninstall X.X.X and install the new one with rvm install X.X.X and make it default by rvm use --default X.X.X.

cheers.

Solution 13 - Ruby on-Rails

I got the same problem for Ruby 2.6.3, nothing listed in answers could help. The only the following solution worked for me:

  1. bundle update rails

  2. Remove Gemfile.lock

  3. bundle

Solution 14 - Ruby on-Rails

I had the same issue. In my Gemfile.lock i saw at the end "bundled with bundler 2.0.2", but running bundle --version gave me version 1.17... For me it solved just updateing my bundler with the following command: bundle update --bundler see bundler documentation

Solution 15 - Ruby on-Rails

I deleted the project and made a git clone from the Heroku app, don´t know if it is a good solution, but it worked for me.

Solution 16 - Ruby on-Rails

I got the same issue in my local system, my ruby version was low due to which the error was occurring. Fixed it by switching it to updated versions of ruby.

Solution 17 - Ruby on-Rails

Using bundler 2.0.1 allows for automatic version switching as required by the lock file. In this regard, installing bundler 2.0.1 worked for me.
Installing bundler 2.0.1
gem install bundler -v 2.0.1
Update bundler
bundle update -bundler

Solution 18 - Ruby on-Rails

I had the same problem today.

In my case the problem was caused by using rvm gemset other than latest I have with ruby 2.7.1 and bundler 2.1.4 (same bundle Gemfile was locked with).

So just take a look at your rvm environment before doing any other solution listed here. Specially if you're running your project on production.

Happy hacks !

Solution 19 - Ruby on-Rails

Delete gem history and modules installed in rails application.

$ rm -rf vendor/bundle
$ rm Gemfile.lock

and, bundle

$ bundle install --path=vendor/bundle

and, start Rails Server

$ bundle exec rails s

and, connect to browser.

http://localhost:3000/

Solution 20 - Ruby on-Rails

Same error, but locally. I finally figured out I was using wrong version of ruby on my command line (I'm using uru to manage ruby versions.) After all, how could the gemfile use and produce a lock file with version 2.1.4, yet my search didn't find that version!

>gem list bundler

*** LOCAL GEMS ***

bundler (default: 1.16.2, 1.13.1)
capistrano-bundler (1.6.0, 1.1.4)

So I changed to the correct version of ruby and all was good.

Remember, gems are stored with your Ruby version!

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionPedroView Question on Stackoverflow
Solution 1 - Ruby on-RailsPromise PrestonView Answer on Stackoverflow
Solution 2 - Ruby on-RailsAlexView Answer on Stackoverflow
Solution 3 - Ruby on-RailsS.YadavView Answer on Stackoverflow
Solution 4 - Ruby on-RailsSergeyView Answer on Stackoverflow
Solution 5 - Ruby on-RailsispirettView Answer on Stackoverflow
Solution 6 - Ruby on-RailsJohn CreamerView Answer on Stackoverflow
Solution 7 - Ruby on-RailsAleksander JessView Answer on Stackoverflow
Solution 8 - Ruby on-RailsJitendra RathorView Answer on Stackoverflow
Solution 9 - Ruby on-RailsArye EidelmanView Answer on Stackoverflow
Solution 10 - Ruby on-RailsAnthonyView Answer on Stackoverflow
Solution 11 - Ruby on-RailsFrederik SpangView Answer on Stackoverflow
Solution 12 - Ruby on-RailsNavid FarjadView Answer on Stackoverflow
Solution 13 - Ruby on-RailsTimo MossView Answer on Stackoverflow
Solution 14 - Ruby on-RailsdctsView Answer on Stackoverflow
Solution 15 - Ruby on-RailsPedroView Answer on Stackoverflow
Solution 16 - Ruby on-RailsDyaniyal WilsonView Answer on Stackoverflow
Solution 17 - Ruby on-RailsMark KariukiView Answer on Stackoverflow
Solution 18 - Ruby on-RailsluilverView Answer on Stackoverflow
Solution 19 - Ruby on-RailsjojoView Answer on Stackoverflow
Solution 20 - Ruby on-RailsdirktayView Answer on Stackoverflow