`bundle platform` doesn't indicate that BUNDLE_FORCE_RUBY_PLATFORM is in effect, and neither does anything else

[robacarp]

Describe the problem as clearly as you can

We recently had a difficult to diagnose problem.

The summary of the issue is this:

• Running on an arm based laptop
• A repo had .bundle/config with BUNDLE_FORCE_RUBY_PLATFORM set
• A gem was added to the repo which had a ruby-platform version, but the ruby-platform version had an amd64 binary in it
• Bundler was installing the incorrect version of the gem

Did you try upgrading rubygems & bundler?

Yep

Which command did you run?

In diagnosing the problem, we ran bundle platform and ruby -e "puts Gem::Platform.local", but they both emitted the expected arm64, even though BUNDLE_FORCE_RUBY_PLATFORM was set to true.

What were you expecting to happen?

The situation is incredibly obscure, but I think looking back to it I would have expected bundle platform to:

• warn about the config override
• or say that it would have installed the ruby platform as configured

What actually happened?

> bundle platform
Your platform is: arm64-darwin-24

Your app has gems that work on these platforms:
* aarch64-linux
* arm-linux
* arm64-darwin
* ruby
* x86-linux
* x86_64-darwin
* x86_64-linux

Your Gemfile specifies a Ruby version requirement:
* ruby 3.3.0

Your current platform satisfies the Ruby version requirement.

[deivid-rodriguez]

I think adding force_ruby_platform information to bundle platform output is indeed a great idea!

Please feel free to give this a try!

[robacarp]

A related message from the tailwind ruby gem:

Tailwindcss::Ruby::ExecutableNotFoundException: Cannot find the tailwindcss executable for aarch64-linux in /usr/local/bundle/gems/tailwindcss-ruby-4.0.12/exe (Tailwindcss::Ruby::ExecutableNotFoundException)

If you're using bundler, please make sure you're on the latest bundler version:

    gem install bundler
    bundle update --bundler

Then make sure your lock file includes this platform by running:

    bundle lock --add-platform aarch64-linux
    bundle install

See `bundle lock --help` output for details.

If you're still seeing this message after taking those steps, try running
`bundle config` and ensure `force_ruby_platform` isn't set to `true`. See
https://github.com/flavorjones/tailwindcss-ruby#check-bundle_force_ruby_platform

I think this is evidence of more confusion around the issue.

[flavorjones]

@robacarp the tailwindcss-ruby gem ships native gems that work, and a "vanilla" ruby gem that emits the above warning when used (because it is a native-only gem). I think things are working as designed in this case.

If you're planning on using a native-only gem like tailwindcss-ruby then you should avoid using BUNDLE_FORCE_RUBY_PLATFORM and instead mark the specific gems for which you want to avoid using a native gem.

[deivid-rodriguez]

My suggestion to improve bundle platform output in this situation would be:

$ bundle platform
Your platform is: arm64-darwin-24
However, your effective platform is: ruby (because force_ruby_platform is set via BUNDLE_FORCE_RUBY_PLATFORM: true)

Your app has gems that work on these platforms:
* aarch64-linux
* arm-linux
* arm64-darwin
* ruby
* x86-linux
* x86_64-darwin
* x86_64-linux

Your Gemfile specifies a Ruby version requirement:
* ruby 3.3.0

Your current platform satisfies the Ruby version requirement.