More recent RubyGems versions are less strict and as long as the major Bundler version in the BUNDLED WITH section of your Gemfile.lock file matches the major Bundler version you are running, it won’t generate an error. $ gem install bundler -v "$(grep -A 1 "BUNDLED WITH" Gemfile.lock | tail -n 1)" Update RubyGems This will be the default behavior of bundle install in the future, but for now you can get that result with: So the most reliable way to fix this error is to install that exact Bundler version. The only version of Bundler 100% guaranteed to work with a given Gemfile.lock file is the Bundler version that generated it. There are a few options, depending on what you are able to update to newer versions. This is a bug, and future Bundler & RubyGems versions will automatically install and use the exact version of Bundler your application needs to run. This error is saying (in a very particular way) that RubyGems was unable to find the exact version of Bundler that is in your Gemfile.lock. If you are using one of those versions of RubyGems, but do not have that exact version of Bundler installed, you will run into this error:Ĭan't find gem bundler (>= 0.a) with executable bundle (Gem::GemNotFoundException) ![]() ![]() Some versions of RubyGems try to use the exact version of Bundler listed in your Gemfile.lock anytime you run the bundle command. $ gem install bundler -v "$(grep -A 1 "BUNDLED WITH" Gemfile.lock | tail -n 1)" What is this error?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |