Articles, notes and random thoughts on Software Development and Technology
If you are packaging a Lambda as a Docker container image, to run locally start with:
docker run -p 9000:8080 your-image-name
And then to test you can post requests to the running container with curl:
curl -XPOST "http://localhost:9000/2015-03-31/functions/function/invocations" -d '{ "example": "value" }'
Lambdas by default do not have write access to the instance filestorage where they are running. They do my default have 512MB of ephemeral storage mounted at /tmp – this space is include in the Lambda runtime costs by default and can be increased (with additional cost) in 1MB increments upto 10GB.
More info here: https://docs.aws.amazon.com/lambda/latest/dg/configuration-function-common.html#configuration-ephemeral-storage
While testing my Lambda using a Docker container, when the Lambda is invoked, I’m getting this runtime error:
Process 17(bootstrap) exited: Runtime exited with error: exit status 127
Process exit status code 127 errors are usually a file not found error. Going back through the Lambda logs, luckily there’s an error telling me I have an error in my shell script:
/var/task/test.sh: line 5: output: command not found
Quick and easy fix.
I’m getting this error when invoking myLambda which is using a Docker container:
Init failed error=fork/exec /var/runtime/bootstrap
To fix this, add a step to make the bootstrap file executable after you copy into the image:
COPY bootstrap ${LAMBDA_RUNTIME_DIR}
RUN chmod +x ${LAMBDA_RUNTIME_DIR}/bootstrap