Skip to content

Commit

Permalink
Fix gem bundle call during packaging
Browse files Browse the repository at this point in the history
We've seen some failures because it was simply using "bundle install"
which does not properly install the gems into BOSH_INSTALL_TARGET.

After upgrading to ruby 3.2 it seems that the gems instead are installed
into /usr/local/bundle which does not transfer from the compilation VM into
the package so when the CPI is later invoked the gems are missing.
  • Loading branch information
jpalermo authored and cunnie committed Apr 15, 2024
1 parent f563c52 commit d3e188a
Showing 1 changed file with 1 addition and 5 deletions.
6 changes: 1 addition & 5 deletions packages/bosh_aws_cpi/packaging
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,6 @@ cp -a bosh_aws_cpi/* ${BOSH_INSTALL_TARGET}

cd ${BOSH_INSTALL_TARGET}

export BUNDLER_VERSION="$(bundle -v | grep -o -e '[0-9.]*')"
bundle config set --local deployment 'true'
bundle config set --local no_prune 'true'
bundle config set --local without 'development test'
bundle config set --local cache_path 'vendor/package'

bundle install
bosh_bundle_local

0 comments on commit d3e188a

Please sign in to comment.