docker image does not include libffi.so.6 needed for Python 3.11

[aws]

docker image does not include libffi.so.6 needed for Python 3.11

[jysheng123]

Hi, thanks for bringing up the issue. It seems that https://gallery.ecr.aws/lambda/python made a release that has issues and should be fixed next release. Until then we have a mitigation. As you can see in the documentation (https://docs.aws.amazon.com/toolkit-for-vscode/latest/userguide/serverless-apps-run-debug-config-ref.html), there is a field is launch.json sam properties called skipNewImageCheck. Add this to your launch.json and set it to be true. Then you have to manually delete the images on your docker locally, both public.ecr.aws/lambda/python:3.11-rapid-x86_64 and public.ecr.aws/lambda/python:3.11-x86_64. After deleting it, you can then pull an older version of the image on their website, for my example I used public.ecr.aws/lambda/python:3.11.2023.11.18.02-x86_64 (change architecture to match yours). After that you have to retag the image to the x86-64 tag itself. Therefore the command should be docker tag <YOUR IMAGE ID> public.ecr.aws/lambda/python:3.11-x86_64. After that, running the debugger should work properly.

After running the steps this is what a sample launch.json and docker images command should output:
{ "configurations": [ { "type": "aws-sam", "request": "direct-invoke", "name": "test", "invokeTarget": { "target": "code", "projectRoot": "hello_world", "lambdaHandler": "app.lambda_handler" }, "lambda": { "runtime": "python3.11", "payload": {}, "environmentVariables": {} }, "sam": { "skipNewImageCheck": true } } ] }
docker images command ouput:
public.ecr.aws/lambda/python 3.11-x86_64 3e02a31fb67a 2 weeks ago 752MB public.ecr.aws/lambda/python 3.11.2023.11.18.02-x86_64 3e02a31fb67a 2 weeks ago 752MB

Please let me know if you have any questions or any issues still. Thanks

[georgetakla]

Thank you jysheng123!
I followed the steps and provided the action log for reference
docker_images_updates.txt

I noticed in the (https://docs.aws.amazon.com/toolkit-for-vscode/latest/userguide/serverless-apps-run-debug-config-ref.html), that we can define for sam the build-image. I have not tested this approach yet and I wonder if you recommend it for specific cases

config will be like
{ "configurations": [ { "type": "aws-sam", "request": "direct-invoke", "name": "test", "invokeTarget": { "target": "code", "projectRoot": "hello_world", "lambdaHandler": "app.lambda_handler" }, "lambda": { "runtime": "python3.11", "payload": {}, "environmentVariables": {} }, "sam": { "skipNewImageCheck": true, "build-image": "http://public.ecr.aws/lambda/python:3.11-x86_64" } } ] }

[jysheng123]

Hi, well turns out the mitigation will not be needed as the lambda aws team has fixed the issue on their side so your original debugger should be working just fine now, I tested it on mine and it works properly. Let me know if your issue is fixed and in regards to your approach, I don't believe there is a build option in sam for build-image. If you want to be able to pass in your custom image, I suggest you do something similar to the mitigation I was talking about, as in tag your custom image as the image that it is looking for (in this case public.ecr.aws/lambda/python:3.11-x86_64) then pass in the skipNewImageCheck as True then it should be using that image. Let me know if your debugger is working properly now.

[georgetakla]

Hi,
1- the mitigation is working for me, thank you!. I did not test the updated image yet
2- in the buildArguments of build option , it points to sam build that has build-image