AWS Lambda Node 16 container image error ( Missing Runtime API Server configuration )

Question

I wanted to create node16 container image for aws lambda. I have following Dockerfile and index.js for lambda function. Building image (docker build -t lambda-hello-world .) works fine but when I invoke( docker run --rm -p 8080:8080 lambda-hello-world ) lambda function it returns error. Could someone please suggest?

2022-05-07T15:56:51.182Z        undefined       INFO    Executing 'index.handler' in function directory '/'
/node_modules/aws-lambda-ric/lib/index.js:42
        throw new Error("Missing Runtime API Server configuration.");
        ^

Error: Missing Runtime API Server configuration.
    at Object.run (/node_modules/aws-lambda-ric/lib/index.js:42:15)
    at Object.<anonymous> (/node_modules/aws-lambda-ric/bin/index.js:14:8)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47```
    enter code here

Dockerfile

FROM node:16-alpine

# Bundle app source
COPY . .

RUN npm install

EXPOSE 8080

ENTRYPOINT ["npx", "aws-lambda-ric"]

CMD ["index.handler"]

index.js

exports.handler = async (event, context) => {
    return `Hello World form node version ${process.version}`;
}

hoangdv · Accepted Answer · 2022-05-08 03:37:45Z

4

According to this issue, whenever your Docker image is invoked, whether in Lambda or on your local machine, you need an entry script that will help your use the RIE proxy when necessary (e.g., on our local machine).

entry.sh in root project:

#!/bin/sh
# Check if the AWS_LAMBDA_RUNTIME_API is not set. This environment
# variable is set when the image is running on Lambda.
if [ -z "${AWS_LAMBDA_RUNTIME_API}" ]; then
  # We know the image is being run off of Lambda, so we need to use the RIE
  # to start the function.
  exec /usr/bin/aws-lambda-rie ./node_modules/.bin/aws-lambda-ric $1
else
  # We know the image is being run on Lambda so we don't need to use the RIE.
  exec ./node_modules/.bin/aws-lambda-ric $1
fi

Your Dockerfile:

FROM node:16-alpine

# Bundle app source
COPY . .

RUN npm install

EXPOSE 8080

# Downloads the Lambda Runtime Interface Emulator (RIE)
ADD https://github.com/aws/aws-lambda-runtime-interface-emulator/releases/latest/download/aws-lambda-rie /usr/bin/aws-lambda-rie

RUN chmod +x /usr/bin/aws-lambda-rie
RUN chmod +x entry.sh

ENTRYPOINT ["entry.sh"]

CMD ["index.handler"]

answered May 8, 2022 at 3:37

hoangdv

16.3k4 gold badges31 silver badges54 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Nagesh Over a year ago

Thank you! let me try this solution and update @hoangdv

Hila Grossbard Over a year ago

this solution worked for me! i only had to change "ENTRYPOINT ["entry.sh"] " to: "ENTRYPOINT [ "bash", "entrypoint.sh" ]" as proposed here: stackoverflow.com/a/53071720/9158986

Collectives™ on Stack Overflow

AWS Lambda Node 16 container image error ( Missing Runtime API Server configuration )

1 Answer 1

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related