Articles, notes and random thoughts on Software Development and Technology
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
When running a ‘docker build . -t imagename’ to build a new image, each of the steps in your Dockerfile outputs a one-line status, but if you need to see the actual output of each step, you need pass the –progress-plain option. If your build is stopping at a particular step and you need to see the output of previous steps that are now cached, you can use the –no-cache option:
docker build --progress=plain --no-cache . -t imagename