Lambda HelloWorld sample : "Error PythonPipBuilder:ResolveDependencies - 'utf-8' codec can't decode byte" running sam build
I am just trying to build the HelloWork lambda function from AWS. The only change I made is the python version : Runtime: python3.12 instead of 3.9 in the original template.yaml file. I got all the others files from the "sam init".
When I try to build I get the following message:
Starting Build use cache
Manifest file is changed (new hash: 3298f13049d19cffaa37ca931dd4d421) or dependency folder (.aws-sam\deps\ffa173cf-c2b2-47e6-abaf-7aeb5e83ac61) is missing for (HelloWorldFunction), downloading dependencies and copying/building
source
Building codeuri: C:\Workspace\Synapps\batch\aws\sam-app\hello_world runtime: python3.12 metadata: {} architecture: x86_64 functions: HelloWorldFunction
Running PythonPipBuilder:CleanUp
Running PythonPipBuilder:ResolveDependencies
Build Failed Error: PythonPipBuilder:ResolveDependencies - 'utf-8' codec can't decode byte 0xe9 in position 1348: invalid continuation byte
CONTEXT : Windows 11 Professional, IntelliJ, SAM CLI, version 1.112.0
- Topics
- ServerlessCompute
- Language
- English
asked 2 years ago1.5K views
- Newest
- Most votes
- Most comments
Try cleaning the build cache and re-building:
sam build --no-cached --debug
- Remiby2 years ago
--force-rm doesn't seem to exist : https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-cli-command-reference-sam-build.html And sam build --no-cached does not work, same error.
- Osvaldo Marte EXPERT2 years ago
Could you please try the following steps and then review the logs generated during the build process?
sam build --no-cached --debug
The error indicates an issue with encoding when resolving dependencies for the Python 3.12 runtime.
- Ensure your system and Docker installation meet the requirements for Python 3.12, such as Docker version 20.10.10 or higher.
- Verify the SAM CLI version is recent enough to support Python 3.12.
- Check if installing dependencies directly with
pip install -r requirements.txtinside a Docker container with the Python 3.12 image has the same issue. - Try simplifying the template to use a minimal "Hello World" type function without external dependencies at first.
- Consider creating a Lambda layer with your dependencies instead of including them directly in the deployment package.
The Python 3.12 runtime made some changes to return Unicode strings directly instead of escaped sequences, which may cause compatibility issues if other components expect the previous behavior. Updating dependent systems, packages or code to support the new return format could help resolve the problem.
I don't know if it will help, but I used the sam build command in the folder created after sam init and received the above error. My solution is I deleted the contents in the requirements.txt file and built it. It ran without problem.
answered 2 years ago
