Michael Hart

You have the same result? `Unexpected end of JSON input`?

That 405 is expected – your curl command is making a GET request, not a POST request

Are you on windows or something? Try `--payload "{}"` instead

Can you try with a simpler handler? Does it work on Lambda itself?

(and are you sure there's not another docker container already running? I noticed you were using `-d` for example)

Just try with a simple handler, like this: ```js exports.handler = async () => console.log('It works!') ```

It doesn't look like you're passing a payload in that last comment. You can try just invoking it with curl to remove the AWS CLI as a factor – you...

@dagda1 how'd you go with this?

@lestersm that's an excellent point – AWS CLI v2 changed the way it deals with payloads. https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration.html#cliv2-migration-binaryparam @dagda1 were you using AWS CLI v2 by any chance?

I added that to the README a while back btw: https://github.com/lambci/docker-lambda#running-in-stay-open-api-mode If that solves your problem, then I'll close this issue as solved