- $COMMAND_PREFIX bin/bundle config set --local path $SHARED_PATH/vendor_bundle
-
- run_and_report "Running bundle install" \
- $COMMAND_PREFIX bin/bundle install --local --quiet
+ "$bundle" config set --local path "$bundle_path"
+
+ # As of April 2024/Bundler 2.4, `bundle install` tends not to install gems
+ # which are already installed system-wide, which causes bundle activation to
+ # fail later. Work around this by installing all gems manually.
+ find vendor/cache -maxdepth 1 -name '*.gem' -print0 \
+ | run_and_report "Installing bundle gems" xargs -0r \
+ gem install --conservative --ignore-dependencies --local --quiet
+ # The earlier `bundle config` should have it looking for installed gems in
+ # the right place. Unset GEM_* now to be sure.
+ unset GEM_HOME GEM_PATH
+ run_and_report "Running bundle install" "$bundle" install --prefer-local --quiet
+ run_and_report "Verifying bundle is complete" "$bundle" exec true