Getting a 502 Bad Gateway response during the local testing of the container based lambda about aws-lambda-runtime-interface-emulator HOT 2 OPEN

Hello @skulkarni56-bb, sorry this issue was not picked up earlier, let us know if you already fixed this issue.
This is a behavior that could happen when the image used is not totally compatible with Lambda (or it doesn't have the right entrypoint), so we would like to ask for more information to further understand the issue
1 Did you use the Dockerfile specified in the RIC instructions from the link you provided?
2 Did you build that Dockerfile first and added its name:tag to the docker run command?
3 If you used a different Dockerfile, what file did you use?
Thank you,

from aws-lambda-runtime-interface-emulator.

Hi, I have the same issue with using the public.ecr.aws/lambda/python:3.8 image.
I can visit http://localhost:9000/2015-03-31/functions/function/invocations with my browser but I cannot Post to the endpoint - it just keeps on going forever:

* Connected to localhost (127.0.0.1) port 9000 (#0)
> POST /2015-03-31/functions/function/invocations HTTP/1.1
> Host: localhost:9000
> User-Agent: curl/7.75.0
> Accept: */*
> Content-Length: 2
> Content-Type: application/x-www-form-urlencoded
>
} [2 bytes data]
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 Connection Established
< Proxy-Agent: Ztunnel/1.0
* no chunk, no close, no size. Assume close to signal end
*

from aws-lambda-runtime-interface-emulator.