`./dlf rake spec` Fails

[Kurt-von-Laven]

I tried following the steps in the contributing guide in order to set up my development environment, and encountered the following error:

$ ./dlf rake spec
/usr/share/rvm/rubies/ruby-3.1.1/bin/ruby -I/usr/share/rvm/gems/ruby-3.1.1/gems/rspec-support-3.11.0/lib:/usr/share/rvm/gems/ruby-3.1.1/gems/rspec-core-3.11.0/lib /usr/share/rvm/gems/ruby-3.1.1/gems/rspec-core-3.11.0/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --color
Could not find addressable-2.8.1, fakefs-1.8.0, webmock-3.18.1, nokogiri-1.13.8-x86_64-linux, rack-3.0.0, rack-test-2.0.2, tomlrb-2.0.3, public_suffix-5.0.0, rspec-expectations-3.11.1, rspec-mocks-3.11.1, parallel-1.22.1, parser-3.1.2.1, rubocop-ast-1.21.0, unicode-display_width-2.3.0, rspec-support-3.11.1 in any of the sources
Run `bundle install` to install missing gems.

While loading ./spec/lib/license_finder/cli/approvals_spec.rb an `exit` / `raise SystemExit` occurred, RSpec will now quit.
Failure/Error: require 'bundler/setup'

SystemExit:
  exit
# ./spec/spec_helper.rb:4:in `<top (required)>'
# ./spec/lib/license_finder/cli/approvals_spec.rb:3:in `<top (required)>'
# ------------------
# --- Caused by: ---
# Bundler::GemNotFound:
#   Could not find addressable-2.8.1, fakefs-1.8.0, webmock-3.18.1, nokogiri-1.13.8-x86_64-linux, rack-3.0.0, rack-test-2.0.2, tomlrb-2.0.3, public_suffix-5.0.0, rspec-expectations-3.11.1, rspec-mocks-3.11.1, parallel-1.22.1, parser-3.1.2.1, rubocop-ast-1.21.0, unicode-display_width-2.3.0, rspec-support-3.11.1 in any of the sources
#   /usr/share/rvm/gems/ruby-3.1.1/gems/bundler-2.3.9/lib/bundler.rb:151:in `setup'
/usr/share/rvm/rubies/ruby-3.1.1/bin/ruby -I/usr/share/rvm/gems/ruby-3.1.1/gems/rspec-support-3.11.0/lib:/usr/share/rvm/gems/ruby-3.1.1/gems/rspec-core-3.11.0/lib /usr/share/rvm/gems/ruby-3.1.1/gems/rspec-core-3.11.0/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --color failed

I had already run bundle install.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.