AWS Lambda container (aws-nuke) exits with Runtime.ExitError even though process returns exit code 0 [closed]

Question

Closed. This question needs debugging details. It is not currently accepting answers.

Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.

Closed 3 months ago.

Improve this question

I have aws-nuke running on Lambda using a container. aws-nuke is returning exit code 0, but the Lambda returns Runtime.ExitError

Cloud watch logs:

...
Scan complete: 221 total, 0 nukeable, 221 filtered.
No resource to delete.
INIT_REPORT Init Duration: 77885.80 ms Phase: invoke Status: error Error Type: Runtime.ExitError
START RequestId: xxx Version: $LATEST
RequestId: xxx Error: Runtime exited without providing a reason Runtime.ExitError
END RequestId: xxx
REPORT RequestId: xxx Duration: 77905.56 ms Billed Duration: 77906 ms Memory Size: 256 MB Max Memory Used: 99 MB

Thank you

Mark B · Accepted Answer · 2025-08-27 15:49:35Z

0

AWS Lambda is not a generic container runtime. The container needs to implement the AWS Lambda runtime API

If you want a more generic serverless container environment, I suggest ECS Fargate

answered Aug 27 at 15:49

Mark B

203k27 gold badges339 silver badges332 bronze badges

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

Collectives™ on Stack Overflow

AWS Lambda container (aws-nuke) exits with Runtime.ExitError even though process returns exit code 0 [closed]

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related