FIX: Use `bundle config` instead of deprecated flags (#598)
authorDavid Taylor <david@taylorhq.com>
Wed, 26 Jan 2022 10:18:49 +0000 (10:18 +0000)
committerGitHub <noreply@github.com>
Wed, 26 Jan 2022 10:18:49 +0000 (10:18 +0000)
commit7ba8d4e926055d0b88b789801f1836d118e309ef
tree08e5f06ee345b1fe5c75a40a95bd9675a3149bda
parenteb643f6478e3d67e4555cfce87f89d77438b1b7f
FIX: Use `bundle config` instead of deprecated flags (#598)

Bundler 2.3.0 started re-installing and re-invoking itself based on the `BUNDLED WITH` declaration in the Gemfile.lock. The second run of bundler doesn't receive the flags from the initial invocation.

These flags were deprecated some time ago. The recommended solution is to use `bundle config`, which persists the config to the filesystem for future invocations to load.
image/base/release.Dockerfile