Repository navigation
Upgrade Alpine packages in the runtime image for OpenSSL fixes - #1808
Closed
helpcodeai wants to merge 1 commit into
Closed
helpcodeai wants to merge 1 commit into
helpcodeai wants to merge 1 commit into
Conversation
7 tasks done
Contributor
Author
|
Folded into the v0.55.7 release PR #1809. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Trivy reports 10 medium alerts on main for OpenSSL (
libssl3/libcrypto33.5.9-r0) in the runtime image. Alpine already ships 3.5.9-r1, but thenode:26-alpinebase image has not picked it up yet, so every new build still carries r0. The runtime stage now runsapk upgrade --no-cachebefore it adds wget.Changes
Dockerfile, runner stage:apk upgrade --no-cache && apk add --no-cache wget.Type
Testing
docker run --rm node:26-alpine sh -c 'apk upgrade --no-cache && apk info -v | grep -E "^lib(ssl|crypto)3"'showslibcrypto3-3.5.9-r1andlibssl3-3.5.9-r1(r0 before the upgrade).Not in this PR: the two high alerts for
effect3.20.0 (pulled in by@prisma/config, used only by the Prisma CLI at migration time). An npm override did not resolve cleanly with npm 11 (--package-lock-onlydrops the package), so that needs its own change or a Prisma patch release.Both deployment modes: same image for Cloud and self-hosted, no behaviour change.
Checklist
Related Issues
Code scanning alerts #757 to #766.