fix: disable library path for node 20-24 images#190
Open
reedham-aws wants to merge 5 commits into
Open
Conversation
Vandita2020
approved these changes
Apr 24, 2026
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
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.
Issue #, if available:
#189 is the PR where we first started seeing failures for node build images.
Description of changes:
It seems like there was a recent update to the Nodejs images using AL2023 that is causing build failures for Node 20, 22, and 24. The issue is that the
dnf installthat's being run when building the image from the Dockerfile is failing because it cannot findOPENSSL_3.4.0. This is actually an issue we experience in another place in the Dockerfiles, and have a workaround for it:aws-sam-build-images/build-image-src/Dockerfile-nodejs20x
Lines 49 to 53 in f11394d
This change makes it so the environment variable that had been interfering with Python and
dnfis unset. For now, I'm not sure if I we should make this change considering it's unsetting a value that's explicitly in the base image, even if it is working.Example of the failed run here:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.