Dockerfile.development: Ignore missing bundle binstub on cleanup #14120
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you trying to accomplish?
The
rm .bundle/bin/bundlecommand fails if the file doesn't exist, breaking the Docker build. Usingrm -fmakes the removal idempotent and prevents build failures when the binstub isn't present.Anything you want to highlight for special attention from reviewers?
Simple one-liner. The
-fflag suppresses errors for missing files while still removing the file when it exists.How will you know you've accomplished your goal?
Before this change, building the UV image locally with
bin/docker-dev-shell uv --rebuildcommand would fail during the dependabot-updater step:1.691 rm: cannot remove '.bundle/bin/bundle': No such file or directoryAfter this change
The
Dockerfile.developmentbuilds successfully regardless of whether the bundle binstub exists.Checklist