docs: clarify distinct purposes of --pull and --no-cache flags#25308
Open
jasdeepbhalla wants to merge 1 commit into
Open
docs: clarify distinct purposes of --pull and --no-cache flags#25308jasdeepbhalla wants to merge 1 commit into
jasdeepbhalla wants to merge 1 commit into
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
the
area/build
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
--pullsection: adds that the flag only affects theFROMinstruction — cachedRUNlayers are still reused. This prevents readers from assuming--pullalone gives them fresh dependencies.--no-cachesection: replaces the "however... doesn't pull a fresh base image" correction with a positive cross-reference to--pull, and reframes the combined usage as two complementary flags rather than a workaround.Issue
Fixes #25291