Bundler 2.6.1 cannot install Bundler 2.5.14

[alexreid]

Describe the problem as clearly as you can

Bundler 2.6.1 cannot install Bundler 2.5.14

Did you try upgrading rubygems & bundler?

Post steps to reproduce the problem

(Tested on ruby 3.3.3 (2024-06-12 revision f1c7b6f435) [x86_64-linux] running on Linux kernel 6.10.14)

1. Install Bundler 2.6.1
2. Attempt to bundle install with a Gemfile.lock created using Bundler 2.5.14

Which command did you run?

bundle install

What were you expecting to happen?

Bundler 2.6.1 to successfully install Bundler 2.5.14, then use Bundler 2.5.14 to install the gems in the lockfile.

What actually happened?

#29 2.493 Bundler 2.6.1 is running, but your lockfile was generated with 2.5.14. Installing Bundler 2.5.14 and restarting using that version.
#29 7.831 Fetching gem metadata from https://rubygems.org/.
#29 7.917 Fetching bundler 2.5.14
#29 8.201 Installing bundler 2.5.14
#29 8.488 /usr/local/rvm/gems/ruby-3.3.3/bin/ruby_executable_hooks:15:in `read': No such file or directory @ rb_sysopen - install (Errno::ENOENT)
#29 8.488       from /usr/local/rvm/gems/ruby-3.3.3/bin/ruby_executable_hooks:15:in `<main>'
#29 ERROR: process "/bin/sh -c gem install bundler && bundle install" did not complete successfully: exit code: 1

If not included with the output of your command, run bundle env and paste the output below

Environment

Bundler             2.5.14
  Platforms         ruby, x86_64-linux
Ruby                3.3.3p89 (2024-06-12 revision f1c7b6f435f1167a0514b39a5f72f55cec4d1426) [x86_64-linux]
  Full Path         /usr/local/rvm/rubies/ruby-3.3.3/bin/ruby
  Config Dir        /usr/local/rvm/rubies/ruby-3.3.3/etc
RubyGems            3.5.11
  Gem Home          /usr/local/rvm/gems/ruby-3.3.3
  Gem Path          /usr/local/rvm/gems/ruby-3.3.3:/usr/local/rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0
  User Home         /root
  User Path         /root/.local/share/gem/ruby/3.3.0
  Bin Dir           /usr/local/rvm/gems/ruby-3.3.3/bin
Tools               
  Git               2.34.1
  RVM               not installed
  rbenv             not installed
  chruby            not installed
  rubygems-bundler  (1.4.5)

Bundler Build Metadata

Built At          2024-06-21
Git SHA           72920bc230
Released Version  true

Bundler settings

build.mysql2
  Set for your local app (/[redacted]/.bundle/config): "--with-openssl-dir=/usr/local/opt/openssl@1.1 --with-mysql-dir=/usr/local/opt/mysql@5.7"

Gemfile

Gemfile

[Redacted]

Gemfile.lock

[Redacted]

RUBY VERSION
ruby 3.3.3p89

BUNDLED WITH
2.5.14

[simi]

ruby_executable_hooks seems rvm related, have you already reported this to rvm?

[deivid-rodriguez]

Yeah, gem uninstall rubygems-bundler executable-hooks should fix the problem.

[DBugger32]

This started occurring yesterday in our builds -- don't think this is an rvm issue -- think it is an issue with bundler trying to reinstall another version.

[deivid-rodriguez]

RVM specific gems like rubygems-bundler and similar are not really supported. They heavily hack into Bundler & RubyGems internals and have been abandoned for years. This issue comes up once in a while (not only when Bundler tries to install a different version of itself, but in other situations too), and it's always resolved by removing those gems.

[DBugger32]

It works when bundler is installed and version is unchanged, but only fails if bundler attempts to install another version -- a functionality that worked perfectly well before 2.6.0. Trying to understand how this relates to how ruby is installed.

[deivid-rodriguez]

Well I have no idea how Bundler 2.6 could have changed anything here, but maybe it makes rubygems-bundler and friends patches behave even worse 🤷‍♂️. In any case, the solution is to remove those gems.

[DBugger32]

Something changed, but I guess 🤷‍♂️ .

Will have to do that -- but it's not as simple as running gem uninstall rubygems-bundler executable-hooks because they are not installed as part of the application.

Appreciate your prompt responses and supporting this library.

[deivid-rodriguez]

No problem! Yeah, they need to be uninstalled in whatever environment it's running into the error.

Just to confirm, which version of Bundler do you have in your Gemfile.lock file? If you downgrade Bundler to a version different from that version in your Gemfile.lock file, but lower than Bundler 2.6.0, then installation of the locked version during bundle install works just fine?

[DBugger32]

I support 20 ruby apps that are dockerized. I noticed the issue yesterday when trivial dependabot bumps (appsignal 4.2.2 to 4.2.3) started having image build failures in our CI. The logs showed the reported error.

We have bundler versions between 2.3.x and 2.5.x in our gemfile.lock files. Our docker builds do a

gem update --system \
  && gem install bundler

before running bundle install.

Prior to yesterday morning we'd get...

Bundler 2.4.10 is running, but your lockfile was generated with 2.3.26. Installing Bundler 2.3.26 and restarting using that version.
08:14:35   #34 2.461 Fetching gem metadata from https://rubygems.org/.
08:14:35   #34 2.522 Fetching bundler 2.3.26
08:14:35   #34 2.652 Installing bundler 2.3.26

the new version of bundler would then happily run bundle install.

So yesterday morning, I went through our active apps and bundled all the gems with 2.6.0, and kicked off the builds. Since bundler didn't have to reinstall a version, everything worked...

...until today, when version 2.6.1 was installed in the container and the error returned because bundler had to install version 2.6.0.

I've reproduced it locally by uninstalling whatever older version of the bundler was used to make the gemfile.lock and get the error as now expected....

bundle install                  
Bundler 2.6.1 is running, but your lockfile was generated with 2.3.23. Installing Bundler 2.3.23 and restarting using that version.
Fetching gem metadata from https://rubygems.org/.
Fetching bundler 2.3.23
Installing bundler 2.3.23
/Users/blah/.rvm/gems/ruby-3.2.2/bin/ruby_executable_hooks:15:in `read': No such file or directory @ rb_sysopen - install (Errno::ENOENT)
	from /Users/blah/.rvm/gems/ruby-3.2.2/bin/ruby_executable_hooks:15:in `<main>'

The interesting thing is, if I then rerun bundle install afterward -- it works without complaint.

So the install of the matching version is mostly working, however it does not work in the context of the original call as it once did.

I spent a little time trying to reproduce the reverse case starting with an older version of bundler -- but goodness bundler just wants to run with the latest version and using the 2.X.X command obviously defeats the purpose.

[deivid-rodriguez]

Something I don't understand, if you're doing gem update --system && gem install bundler in your Dockerfile, it's strange that you were running Bundler 2.4.10, no? The previous latest version was 2.5.23.

According to your explanation, it could've been any change in between 2.4.10 and 2.6.0 that triggered this, right?

Did you try adding gem uninstall rubygems-bundler gem-wrappers executable-hooks to your Dockerfile? That should fix things.

I don't plan to add any changes to support these gems. Instead, I plan to move forward with #7752, since I think it's the same functionality these gems want to provide, and then ask RVM to stop installing these gems by default.

[DBugger32]

I just pulled an old log file i had lying around for an example.

This started breaking with 2.6.0.

Since it has been clear I have to live with the new normal -- I've updated our CI process to grab the bundler version from the gemfile.lock and pass it in as an argument to the docker build and just install the version I need.

gem update --system \
  && gem install bundler -v $BUNDLER_VERSION

[deivid-rodriguez]

I just pulled an old log file i had lying around for an example.

Ah, I see. Ok.

I spent a little time trying to reproduce the reverse case starting with an older version of bundler -- but goodness bundler just wants to run with the latest version and using the 2.X.X command obviously defeats the purpose.

You could downgrade the latest version with gem update --system 3.5.23 && gem uninstall bundler:2.6.0 bundler:2.6.1.

This started breaking with 2.6.0.

I totally believe you about Bundler 2.6.0 making this stop working, I just don't know how since I'm unfamiliar to how all these gems modify Bundler & RubyGems. It's surprising though, I wasn't expecting the kind of changes that went into this version to break things like this.

I've updated our CI process to grab the bundler version from the gemfile.lock and pass it in as an argument to the docker build and just install the version I need.

Cool, that seems like it would work too. I still recommend to completely get rid of these gems, they have caused other issues in the past and are likely to break again.

[DBugger32]

I am sure this not the last you are going to hear of this.

[deivid-rodriguez]

@DBugger32 Thanks for willing to help reproduce this and providing feedback, I will try to reproduce this myself so I can at least better document this problem since I'm too curious now 😅!

I am sure this not the last you are going to hear of this.

Most likely, we'll see!