Remove redundant apk update in Dockerfiles (cc #5016)
#9055
Conversation
This file contains 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
The `apk` commands can utilize the `--no-cache` option, making the `update` step superfluous and ensuring the latest packages are used without maintaining a local cache. An additional `apk update` in the Dockerfile will just make the image larger with no benefits.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Title
Remove redundant
apk updatein Dockerfiles (cc #5016)Type
🧹 Refactoring
🚄 Infrastructure
Changes
The
apkcommands can utilize the--no-cacheoption, making theupdatestep superfluous and ensuring the latest packages are used without maintaining a local cache. An additionalapk updatein the Dockerfile will just make the image larger with no benefits.