You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Instead of podman, the docker command should also work.)
Output:
=== BUNDLE_FROZEN=1 ===
=== bundle --version ===
4.0.11
=== bundle check ===
The Gemfile's dependencies are satisfied
Cannot write a changed lockfile while frozen.
=> exit=0
=== bundle install ===
Your lockfile is missing a CHECKSUMS entry for "rake", but can't be updated
because frozen mode is set
Run `bundle install` elsewhere and add the updated Gemfile.lock to version
control.
=> exit=16
Describe the problem as clearly as you can
BUNDLE_FROZEN=1 bundle checkexits with 0 status, even when someCHECKSUMSentry is missing inGemfile.lock.Did you try upgrading rubygems & bundler?
Yes, the issue occurs in the latest Bundler 4.0.11.
Post steps to reproduce the problem
Dockerfile:Build and run:
podman build -t bundler-repro . podman run --rm --env BUNDLE_FROZEN=1 bundler-repro(Instead of
podman, thedockercommand should also work.)Output:
Please note that
=> exit=0withbundle check.Gemfile.lockdiff:Note
The same issue is reproduced against Bundler 2.7.2 with
podman build --build-arg BUNDLER_VERSION=2.7.2.Which command did you run?
What were you expecting to happen?
bundle checkshould exit non-zero in the frozen mode ifCHECKSUMSis invalid, likeexit=16withbundle install.What happened instead?
Like the example above, the command outputs the following and exits 0:
If not included with the output of your command, run
bundle envand paste the output belowI think the info above is sufficient, but you can get the similar info via: