- $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
-
- # As of April 2024/Bundler 2.4, for some reason `bundle install` skips
- # zlib if it's already installed as a system-wide gem, which it often will
- # be because arvados gems pull it in. If this happened, install it in the
- # bundle manually as a workaround.
- if ! $COMMAND_PREFIX bin/bundle info zlib >/dev/null 2>&1; then
- local RUBY_VERSION="$($COMMAND_PREFIX ruby -e 'puts RUBY_VERSION')"
- run_and_report "Adding zlib to bundle" \
- $COMMAND_PREFIX gem install \
- --install-dir="$SHARED_PATH/vendor_bundle/ruby/$RUBY_VERSION" \
- vendor/cache/zlib-*.gem
- fi
+ "$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 \
+ --install-dir="$bundle_path/ruby/$(ruby -e 'puts RUBY_VERSION')"
+ run_and_report "Running bundle install" "$bundle" install --prefer-local --quiet
+ run_and_report "Verifying bundle is complete" "$bundle" exec true