Docs - Wrong ENTRYPOINT in the Dockerfile example

[nic-lan]

While trying to build a valid custom ruby image i found out that the ENTRYPOINT of the Dockerfile example in the readme is not valid.

In my case the gem install aws_lambda_ric put the the gem into usr/local/bundle/bin and not in usr/local/bin

So to make it work i had to change the entrypoint from

ENTRYPOINT ["/usr/local/bin/aws_lambda_ric"]

to

ENTRYPOINT [ "/usr/local/bundle/bin/aws_lambda_ric" ]

Can i open a PR on the README with the above change proposals ?

Maybe someone can find that useful.

[yebityon]

Thanks a lot. It was really helped :)

[tosh2230]

I tried it with the amazonlinux image used in the README and it worked fine, so I suspect that the ENTRYPOINT in the README is correct.

Then, I changed the base image to ruby:2.7-slim, I got the following error when running the Lambda function:

{
  "errorMessage": "RequestId: xxxxxxxx-xxxx-0000-xxxx-xxxxxxxxxxxx Error: fork/exec /usr/local/bin/aws_lambda_ric: no such file or directory",
  "errorType": "Runtime.InvalidEntrypoint"
}

In this case, changing the ENTRYPOINT to /usr/local/bundle/bin/aws_lambda_ric resolved the error. I think this issue is talking about something similar to the error and fix above. The installation destination changes depending on the base image, and it is necessary to match the ENTRYPOINT to it.

[kkan]

With ruby:3.3 image I had to change ENTRYPOINT to /var/lang/bin/aws_lambda_ric