Hi michael.sweeney,
The error message about GLIBC_2.33 not found
occurs because the version of the cryptography
Python package (or other related modules like azure-identity
) used in your Azure Function requires a newer version of the GNU C Library (glibc
) than what is currently available in the Azure Functions Linux runtime environment.
This causes compatibility issues when your function runs, leading to the error you’re seeing.
To resolve this, please try the following steps:
Use Remote Build :
Let Azure build your app’s dependencies in its own environment. This ensures compatibility with the runtime’s system libraries.
Change Your Pipeline Build Agent :
If you use Azure Pipelines, set the build agent image to Ubuntu 20.04 (vmImage: 'ubuntu-20.04'
) instead of ubuntu-latest
. This matches the Azure runtime better and avoids version mismatches.
Pin Cryptography Version :
In your requirements.txt
, set cryptography==43.0.3
to use a version compatible with Azure Functions.
Clean Local Builds Before Deploying :
Remove any locally built packages before deploying to avoid shipping incompatible binaries.
To help you better understand, kindly refer to the documentations below:
- Troubleshoot Python errors in Azure Functions (python-mode-configuration)
- Troubleshoot Python errors in Azure Functions (python-mode-decorators)
- Troubleshoot common issues during Azure Runtime upgrade
More detailed guidance can be found in the Azure Functions Deployment Documentation and the GitHub issue you referenced.
After applying these changes, please redeploy your function app. This approach has helped many customers resolve the GLIBC_2.33
error with Python Azure Functions.
Please let me know incase of further queries, I would be happy to assist you.