Upgrading to 4.0.0 appears to break lambdas using docker

Open
#170 15 comments 6 reactions 1 assignee View on GitHub

@godcrampy is already working on this.

Since Dec 11, 2025.

Assessment

This issue has not been assessed yet.

Description

bug

I had been using

RUN npm install -g aws-lambda-ric

Which is on me for not pinning it to a specific version, but with this after the 4.0.0 release on a new build of an image the lambda will no longer start.

2025-12-06T02:12:47.652Z | npm error could not determine executable to run
-- | --
  | 2025-12-06T02:12:47.653Z | npm error A complete log of this run can be found in: /tmp/.npm/_logs/2025-12-06T02_12_46_306Z-debug-0.log
  | 2025-12-06T02:12:47.664Z | INIT_REPORT Init Duration: 1421.03 ms Phase: init Status: error Error Type: Runtime.ExitError

Pinning to 3.3.0 allows our service to run.

RUN npm install -g aws-lambda-ric@3.3.0

This is across multiple projects for separate company stacks I am seeing this. I've pinned to 3.3.0 across the board.

This is running with node:24 as a base image, and had experienced with a node:23 deployment.

Here is an example of what is being used for the entrypoint with aws-lambda-ric:

ENTRYPOINT ["/usr/local/bin/npx", "aws-lambda-ric"]
CMD ["lib/serverless/lambda/lambda.handler"]

Noting again that after pinning the lambdas work as expected.

This is too similar to the pattern shown here, where the version is unpinned:

https://github.com/aws/aws-lambda-nodejs-runtime-interface-client/blob/a4560c87426fa0a34756296a30d7add1388e575c/README.md?plain=1#L102

Dominant language
TypeScript
Stars
224
Forks
60
Avg merge
26m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-nodejs-runtime-interface-client

All issues in aws/aws-lambda-nodejs-runtime-interface-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.