Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running SAM CLI commands within the Nodejs20.x Build Image #116

Open
hnnasit opened this issue Nov 20, 2023 · 1 comment
Open

Running SAM CLI commands within the Nodejs20.x Build Image #116

hnnasit opened this issue Nov 20, 2023 · 1 comment

Comments

@hnnasit
Copy link
Contributor

hnnasit commented Nov 20, 2023

NOTE: This issue only impacts use cases that use the Nodejs20.x Build Image to run SAM CLI commands excluding sam build. If you are using other Build Images or are using sam build --use-container for your Nodejs20.x Lambda applications, you are not impacted.

Due to different OpenSSL versions required by Node.js and Python within the Nodejs20.x Build Image, SAM CLI commands that involve making network calls (e.g. sam init, sam deploy) will fail. We are working to fix the issue.

For workaround, if your use case requires using these impacted commands within the Nodejs20.x Build Image, please set the environment variable LD_LIBRARY_PATH to empty for that command. For example, LD_LIBRARY_PATH= sam deploy.

@hnnasit hnnasit added stage/needs-triage Automatically applied to new issues and PRs, indicating they haven't been looked at. and removed stage/needs-triage Automatically applied to new issues and PRs, indicating they haven't been looked at. labels Nov 20, 2023
@hnnasit hnnasit pinned this issue Nov 20, 2023
@Dec209
Copy link

Dec209 commented Feb 20, 2024

it's resolved with the new version of the image.

image: public.ecr.aws/sam/build-nodejs20.x:1.109.0-20240206202436

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants