Support for `nodejs16.x`

[rohanshiva]

When running this extension with nodejs16.x, getting Error: Runtime exited with error: exit status 254 Runtime.ExitError. But it works with nodejs14.x. Did anyone face this issue before? @bnusunny

run.sh

#!/bin/bash

npm run start -- --port 8080

[bnusunny]

This error means the node.js process is terminated. Did you try the expressjs-zip example with nodejs16.x runtime?

[rohanshiva]

Yea I tried the express example as well with the zip option and it only works when the base lambda image is running v16.15.0. I noticed that sometimes the lambda function runs on v16.16.0, and that is when this error occurs. I am able to figure out the exact version of node because I ingested the following piece of code in run.sh

#!/bin/bash

node --version
npm run start

I also found this and ran into the same issue when using docker image on lambda with this extension and node v16.16.0 and it seems like the culprit is node v16.16.0. https://repost.aws/questions/QUtlb2BYIEQjyirCUWspC-CQ/exit-254-lambda-error-with-no-extra-explanations

Not sure if there is any way to force the lambda function to use just node v16.15.0 always.

[bnusunny]

No. Lambda service team manages the updates to the managed runtimes. If you need to use a specific version of node.js, lambda docker image is the way to go.

I just did a few quick tests. For expressjs-zip example, I didn't run into v16.16.0 and it worked without errors. For expressjs (docker image) example, I updated the base image to public.ecr.aws/docker/library/node:16.16.0-slim and it also worked with no problem.

Could you try this base image with your function?
public.ecr.aws/docker/library/node:16.16.0-slim

[rohanshiva]

I tried it with the non-slim version and it didn't work, over the last two days I didn't run into v16.16.0 either. I wish there was a way to force/know when the lambda-managed runtime will change. Thank you so much for trying to help me resolve this issue! I will close this issue as it seems like it is not an issue with the extension.

[rohanshiva]

this is the docker file I used

FROM public.ecr.aws/docker/library/node:16.16.0
COPY --from=public.ecr.aws/awsguru/aws-lambda-adapter:0.3.3 /lambda-adapter /opt/extensions/lambda-adapter
EXPOSE 8080
WORKDIR "/var/task"
ADD src/package.json /var/task/package.json
ADD src/package-lock.json /var/task/package-lock.json
RUN npm install --production
ADD src/ /var/task
CMD ["npm","run","start"]

[rohanshiva]

I even tried to explore the logs to see why the any npm command is failing by ingesting this into the index.js file:

exec("npm run start", (error, stdout, stderr) => {
    if (error) {
        console.log(`${stdout}`)
        console.log(`${stderr}`)
        console.log(`error: ${error}`);
        return;
    }
    if (stderr) {
        console.log(`stderr: ${stderr}`);
        return;
    }
    console.log(`stdout: ${stdout}`);
});

but all I see is this

error: Error: Command failed: npm run start

[rohanshiva]

@bnusunny do you know how I can run this extension with the lambda-managed node base images (as in how can I override the entryfile)? I want to test it by building that Docker file locally.

[bnusunny]

Just replace CMD ["npm","run","start"] with ENTRYPOINT ["npm","run","start"].

What does npm run start actually run?

[rohanshiva]

It runs node index.js. It doesn't matter what it runs, even npm --version will fail. Thank you for that

[bnusunny]

@rohanshiva I can reproduce the error with your Dockerfile. The problem seems with NPM. When I replace CMD ["npm","run","start"] with CMD ["node","index.js"], the function works. Please try this with your function.

[rohanshiva]

Yes, I agree the problem is with NPM, but I need to use NPM for my use case which runs next start in the background. I used node index .js in this issue, so that it's simpler to understand and reproduce. I want to essentially run next start through npm run start. Thank you for your help!

[bnusunny]

For next.js, you can build it in standalone mode. It will generate a server.js file and you can just run it as a normal node server: node server.js. I have a simple next.js 12 demo. I can push it up if you want to try it.

[rohanshiva]

Sure, that would be great!