janaz / aws-lambda-node-runtime Goto Github PK
View Code? Open in Web Editor NEWNode implementation of the AWS Lambda runtime
License: Apache License 2.0
aws-lambda-node-runtime's People
Contributors
Stargazers
Watchers
aws-lambda-node-runtime's Issues
Jessie debian image doesn't work anymore due to changes in the mirror network
Running the following (I tried to compile for node 6.10.3):
./auto/package
+ export NODE_VERSION=6.10.3
+ NODE_VERSION=6.10.3
+ export SHA256=faddbe418064baf2226c2fcbd038c3ef4ae6f936eb952a1138c7ff8cfe862438
+ SHA256=faddbe418064baf2226c2fcbd038c3ef4ae6f936eb952a1138c7ff8cfe862438
+++ dirname ./auto/package
++ cd ./auto
++ pwd
+ DIR=/Users/vadorequest/dev/aws-lambda-node-runtime/auto
+ cd /Users/vadorequest/dev/aws-lambda-node-runtime/auto/..
+ docker-compose build
Building package
Step 1/2 : FROM node:10.14.0-slim@sha256:5aaef0bf16a700696c76e0902241aef6f4067e7e13255bddab835080b4a8ed1b
sha256:5aaef0bf16a700696c76e0902241aef6f4067e7e13255bddab835080b4a8ed1b: Pulling from library/node
a92a4af0fb9c: Pull complete
ca548e841944: Pull complete
7d9b18497123: Pull complete
f9cebcc3b850: Pull complete
93c1ded7fca2: Pull complete
Digest: sha256:5aaef0bf16a700696c76e0902241aef6f4067e7e13255bddab835080b4a8ed1b
Status: Downloaded newer image for node:10.14.0-slim@sha256:5aaef0bf16a700696c76e0902241aef6f4067e7e13255bddab835080b4a8ed1b
---> f7c1977f9320
Step 2/2 : RUN apt-get update && apt-get install -y p7zip-full curl xz-utils && apt-get clean all
---> Running in b9394694d065
Ign http://deb.debian.org jessie InRelease
Get:1 http://deb.debian.org jessie-updates InRelease [7340 B]
Get:2 http://security.debian.org jessie/updates InRelease [44.9 kB]
Get:3 http://deb.debian.org jessie Release.gpg [2420 B]
Get:4 http://deb.debian.org jessie Release [148 kB]
Get:5 http://deb.debian.org jessie/main amd64 Packages [9098 kB]
Get:6 http://security.debian.org jessie/updates/main amd64 Packages [825 kB]
W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
Fetched 10.1 MB in 5s (1819 kB/s)
ERROR: Service 'package' failed to build: The command '/bin/sh -c apt-get update && apt-get install -y p7zip-full curl xz-utils && apt-get clean all' returned a non-zero code: 100
The issue seems to be due to a very recent change made in March 2019, see https://unix.stackexchange.com/questions/508724/failed-to-fetch-jessie-backports-repository
[Feature Request] AWS Lambda Docker image / Dockerfile
Is there any way to use this to build a Docker image for Lambda running v15?
Here are the existing images from AWS
Here are the Base Container Images
It would be really cool to have v15 in combination of a size of 10GB in Lambda!
Error: Runtime exited with error: exit status 1
I successfully deployed a runtime for node 6.10.3, thanks a lot for this repository, helped me get started much faster.
I'm encountering an issue though, at runtime.
RequestId: 0e7ebd04-d9a3-4abf-be30-e513e494ea29 Error: Runtime exited with error: exit status 1
Runtime.ExitError
Runtime starting
START RequestId: 8583b34c-2a4b-4568-8f4f-a4d549fca400 Version: $LATEST
Failed to send the response TypeError: Converting circular structure to JSON
at Object.stringify (native)
at Promise (/opt/runtime.js:26:22)
at request (/opt/runtime.js:19:10)
at sendSuccessResponse (/opt/runtime.js:78:3)
at callHandler.then (/opt/runtime.js:171:18)
at process._tickCallback (internal/process/next_tick.js:109:7)
2019-04-09 11:26:32 request received http://staging.unly.org/favicon.ico
2019-04-09 11:26:32 serving page http://staging.unly.org/favicon.ico
Failed to send the response TypeError: Converting circular structure to JSON
at Object.stringify (native)
at Promise (/opt/runtime.js:26:22)
at request (/opt/runtime.js:19:10)
at sendSuccessResponse (/opt/runtime.js:78:3)
at callHandler.then (/opt/runtime.js:171:18)
at process._tickCallback (internal/process/next_tick.js:109:7)
2019-04-09 11:26:32 page served http://staging.unly.org/favicon.ico
next-warm-up-time: 376.293ms
/var/task/node_modules/aws-serverless-express/index.js:87
context.succeed(successResponse)
^
TypeError: context.succeed is not a function
at IncomingMessage.response.on.on (/var/task/node_modules/aws-serverless-express/index.js:87:21)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
END RequestId: 8583b34c-2a4b-4568-8f4f-a4d549fca400
REPORT RequestId: 8583b34c-2a4b-4568-8f4f-a4d549fca400 Duration: 481.14 ms Billed Duration: 500 ms Memory Size: 1024 MB Max Memory Used: 98 MB
RequestId: 8583b34c-2a4b-4568-8f4f-a4d549fca400 Error: Runtime exited with error: exit status 1
Runtime.ExitError
Runtime starting
I don't get those errors when using the native nodejs6.10 AWS Lambda runtime. Any idea what could go wrong? I don't really know how to debug this.
lambda:GetLayerVersion Error when adding as a layer
Hi, I am trying to add the latest US East 1 ARN to a Lambda function but receiving the error: lambda:GetLayerVersion. I tried with 2 different AWS accounts. Can you confirm that the layer is published with public access.
Thanks :)
How to deploy the runtime publicly?
I'd like to deploy the runtime so that it is public.
I've followed the steps 1 to 3, and released my own node 6.10.3 layer runtime. See https://github.com/UnlyEd/aws-lambda-node-runtime-v6.10.3#3-share
The arn that AWS provided me is arn:aws:lambda:eu-west-1:035907498810:layer:node-6-10-3-runtime:1
I tried using this arn in another project but I get Couldn't find valid bootstrap, as if the pull had failed.
I didn't try step 4, because I'm not sure how to replace --role arn:aws:iam::356111732087:role/lambda-role that is specific to your AWS Account.
So, I believe I published a runtime layer that is only available through my own AWS Account? If I can just share it publicly that'd be better. But maybe I misunderstood something.
How to find Checksum for a different version of node?
I'm trying to use the node:10.15.3-jessie image, at https://github.com/nodejs/docker-node/blob/170ed2092d4925971f9cd3ad5dfc416e820f90fd/10/jessie/Dockerfile
I found the official checksum list at https://nodejs.org/dist/v6.10.3/SHASUMS256.txt
But I don't really know what I'm doing and don't know which checksum is the right one, here is the error message:
./auto/package
+ export NODE_VERSION=6.10.3
+ NODE_VERSION=6.10.3
+ export SHA256=5aaef0bf16a700696c76e0902241aef6f4067e7e13255bddab835080b4a8ed1b
+ SHA256=5aaef0bf16a700696c76e0902241aef6f4067e7e13255bddab835080b4a8ed1b
+++ dirname ./auto/package
++ cd ./auto
++ pwd
+ DIR=/Users/vadorequest/dev/aws-lambda-node-runtime/auto
+ cd /Users/vadorequest/dev/aws-lambda-node-runtime/auto/..
+ docker-compose build
Building package
Step 1/2 : FROM node:10.15.3-jessie
---> 5c6c62fac703
Step 2/2 : RUN apt-get update && apt-get install -y p7zip-full curl xz-utils && apt-get clean all
---> Using cache
---> 27fc07f61382
Successfully built 27fc07f61382
Successfully tagged aws-lambda-node-runtime_package:latest
Building runtime-api
Step 1/2 : FROM node:10.15.3-jessie
---> 5c6c62fac703
Step 2/2 : RUN apt-get update && apt-get install -y p7zip-full curl xz-utils && apt-get clean all
---> Using cache
---> 27fc07f61382
Successfully built 27fc07f61382
Successfully tagged aws-lambda-node-runtime_runtime-api:latest
Building dev
Step 1/2 : FROM node:10.15.3-jessie
---> 5c6c62fac703
Step 2/2 : RUN apt-get update && apt-get install -y p7zip-full curl xz-utils && apt-get clean all
---> Using cache
---> 27fc07f61382
Successfully built 27fc07f61382
Successfully tagged aws-lambda-node-runtime_dev:latest
+ docker-compose run --rm -e NODE_VERSION -e SHA256 package
+ dirname auto/package-cmd
+ cd auto
+ pwd
+ DIR=/app/auto
+ cd /app/auto/..
+ tmp_dir=tmp
+ stage_dir=stage/work
+ node_dir=tmp/6.10.3
+ node_archive=node-v6.10.3-linux-x64.tar.xz
+ [ ! -f tmp/node-v6.10.3-linux-x64.tar.xz ]
+ echo 5aaef0bf16a700696c76e0902241aef6f4067e7e13255bddab835080b4a8ed1b tmp/node-v6.10.3-linux-x64.tar.xz
+ sha256sum -c -
tmp/node-v6.10.3-linux-x64.tar.xz: FAILED
sha256sum: WARNING: 1 computed checksum did NOT match
I basically updated the auto/package file and changed the node version to use, without updating the checksum
export NODE_VERSION=6.10.3
export SHA256=faddbe418064baf2226c2fcbd038c3ef4ae6f936eb952a1138c7ff8cfe862438
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.