Bundler 2 is already installed, still getting "You must use Bundler 2 or greater with this lockfile" error

[stuartweir]

After installing Bundler following the steps from this page, I cannot seem to run a test in rails.

The Gemfile.lock states at the bottom:

BUNDLED WITH
   2.0.1

Bundler Version:

$ bundler -v
Bundler version 2.0.1

Rails Test failing even though Bundler 2 is installed

$ bundle exec bin/rails test test/lib/my_rails_test_test.rb
You must use Bundler 2 or greater with this lockfile.

I have tried uninstalling and reinstalling Bundler:

$ gem uninstall bundler && gem install bundler
Successfully uninstalled bundler-2.0.1
Fetching bundler-2.0.1.gem
Successfully installed bundler-2.0.1
Parsing documentation for bundler-2.0.1
Installing ri documentation for bundler-2.0.1
Done installing documentation for bundler after 5 seconds
1 gem installed

Ruby version:

$ ruby -v
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin15]

I'm really not sure what seems to be the issue here, or why it's failing. Any help appreciated.

[stuartweir]

Looks like it might be somehow falling back on an old bundler?

$ gem list bundler

*** LOCAL GEMS ***

bundler (2.0.1, default: 1.17.3, 1.7.3)
capistrano-bundler (1.5.0, 1.3.0, 1.2.0)

not sure how to set/force bundler to use 2.0.1

[hewrin]

I am seeing a similar issue as well, if I delete Gemfile.lock and run bundle again, it says

BUNDLED WITH
   1.16.0

Which is my old version of bundler

[morgoth]

I have the same issue when using Rails and bin/* scripts in app.

Using bundler 2.0.1 with "2.0" mode on Rails 5.2.2 on Ruby 2.6.1

[deivid-rodriguez]

Hello! I tried reproducing this with a fresh Rails app and couldn't, can someone provide reproduction steps? Thanks!

[morgoth]

Not sure why, but I have to skip setting up spring, so here are the steps:

ruby -v
# => ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-linux]
gem -v
# => 3.0.1
bundle -v
# => Bundler version 2.0.1
rails -v
# => Rails 5.2.2
rails new problem --skip-spring
cd problem
bin/rails stats
# => You must use Bundler 2 or greater with this lockfile.

[deivid-rodriguez]

Reproduced now! Thanks! I'll look into it!

[deivid-rodriguez]

Seems like a generic problem with binstubs. Simpler repro:

ruby -v
# => ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-linux]
gem -v
# => 3.0.1
bundle -v
# => Bundler version 2.0.1
rake --version
# => rake, version 12.3.2
mkdir problem
cd problem
echo -e "source 'https://rubygems.org'\ngem 'rake'" > Gemfile
bundle
# => Fetching gem metadata from https://rubygems.org/.
# => Resolving dependencies...
# => Using rake 12.3.2
# => Using bundler 2.0.1
# => Bundle complete! 1 Gemfile dependency, 2 gems now installed.
# => Use `bundle info [gemname]` to see where a bundled gem is installed.
bundle binstubs rake
bin/rake --version
# => You must use Bundler 2 or greater with this lockfile.

[deivid-rodriguez]

Generating a bundler binstub with bundle binstubs bundler fixes the problem. @segiddins @indirect Is this expected?

If it is, I think we need to at least generate a bundler binstub together with any other binstub if it doesn't exist? 🤔. And in any case, we should probably downgrade this error to a warning for now?

[connorshea]

Yup, I had the same problem when using bin/webpack-dev-server provided by webpacker. I ran into it while trying out Docker over the weekend so I thought I had done something wrong 😅

[mbell697]

I don't think this is limited to a binstub issue, in an empty directory with no non-default gems installed:

❯ ruby --version
ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-darwin18]
❯ gem list
*** LOCAL GEMS ***

bigdecimal (default: 1.4.1)
bundler (default: 1.17.2)
*snip*
❯ gem install bundler
Fetching bundler-2.0.1.gem
Successfully installed bundler-2.0.1
Parsing documentation for bundler-2.0.1
Installing ri documentation for bundler-2.0.1
Done installing documentation for bundler after 2 seconds
1 gem installed
❯ gem list
*** LOCAL GEMS ***

bigdecimal (default: 1.4.1)
bundler (2.0.1, default: 1.17.2)
*snip*
❯ ruby -rbundler -e 'puts Bundler::VERSION'
2.0.1
❯ ruby -rbundler/setup -e 'puts Bundler::VERSION'
1.17.2

Why is bundler/setup switching versions?

Adding a gemfile:

❯ echo "source 'https://rubygems.org'" > Gemfile
❯ bundle install
The Gemfile specifies no dependencies
Resolving dependencies...
Bundle complete! 0 Gemfile dependencies, 1 gem now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
❯ cat Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:

PLATFORMS
  ruby

DEPENDENCIES

BUNDLED WITH
   2.0.1
❯ ruby -rbundler -e 'puts Bundler::VERSION'
2.0.1
❯ ruby -rbundler/setup -e 'puts Bundler::VERSION'
You must use Bundler 2 or greater with this lockfile.

Did something change about how bundler/setup is supposed to be used?

[mbell697]

Strangely, requiring bundler before bundler/setup works correctly. This is with a 2.0.1 lock file from above but also results in 2.0.1 loaded without a lock file and correctly loads 1.17.2 with a lock file that specifies that version:

❯ ruby -r bundler -r bundler/setup -e 'puts Bundler::VERSION'
2.0.1

EDIT: In playing with this some more I'm fairly confident this is the problem.

require 'bundler'
require 'bundler/setup`

Works as expected, just require 'bundler/setup' does not. The binstub stuff seemed to solve the problem since somewhere in the new bin stubs require 'bundler' is present so it was loaded by the time the app runs require 'bundler/setup'.

[deivid-rodriguez]

Thanks for your investigations, I'll have another look tomorrow!

[stuartweir]

So, an update at least for my purpose, which doesn't actually solve the problem, but solved it for me.

Steps I took, in exact order:

1. Uninstall bundler
2. Uninstall ruby using rbenv
3. Uninstall rbenv (so, essentially, going bac to MacOS's base installed Ruby. 2.3.x
4. Re-install rbenv
5. Re-install ruby 2.4.1 using rbenv
6. Re-install bundler
7. bundle install

[mbell697]

This seems like a wonky issue so I'm unsure how to open a PR but here is what I believe the issue / fix is:

Rubygems keeps a map of files from default gems and detects them to allow overriding with a normal gem, see: https://github.com/rubygems/rubygems/blob/master/lib/rubygems/core_ext/kernel_require.rb#L39 and
https://github.com/rubygems/rubygems/blob/master/lib/rubygems.rb#L1240

This map is built from the files entry in the gemspec, and bundler is missing an entry for bundler/setup. In 1.17.2 it look likes this: s.files = ["bundler.rb".freeze, "exe/bundle".freeze, "exe/bundler".freeze] adding bundler/setup to the list locally resolves this issue but an actual fix for this, at least as I understand it, means updating the spec file that is shipped with Ruby so likely requires a 1.17.x bundler release that would need to be included in a Ruby 2.6.x release. Though I'm not terribly familiar with how default gem versioning is handled so perhaps I'm wrong here.

In the shorter term this may break a lot of stuff but at least the workaround is rather simple in that you just need to add require 'bundler' prior to require 'bundler/setup'.

I haven't tested it but users of bundler/inline also seem likely to hit this issue.

[deivid-rodriguez]

Thanks so much @mbell697, your diagnosis is perfect! I making some checks now to try figure out the best way to fix this 👍.