- Newest
- Most votes
- Most comments
Hello,
Tim here on the AWS Support Team.
I worked with a few colleagues here at AWS and I do see our AWS ECR Dotnet 6 base image (https://gallery.ecr.aws/lambda/dotnet) includes openldap.
When you mention it’s natively installed I understand that to mean you’re using the one we included when you run your code (so you’ve built your code around the provided openldap package).
The recommendation is to add the following line to your Dockerfile to install openldap, regardless if we include it (so that you’re in total control of your dependencies):
RUN yum install -y openldap
Should the openldap ever be removed from the base image, you bundling it will guarantee it’s always included and installed during your images’ build process.
Just need to note that software development is a bit difficult to troubleshoot and goes a bit easier in the scenario of pair programming (where I’d be right there with you) but I’ve been looking into this on my side my level best.
-
Assuming that you do get it included modifying the Dockerfile, the error does mention to consider setting the LD_DEBUG environment variable.
-
Another item is perhaps permissions on the file, I’ve seen a similar error with our ZIP based Python deployment packages where permissions needed to be changed ( https://aws.amazon.com/premiumsupport/knowledge-center/lambda-deployment-package-errors/ )
-
The final item that could be the cause is how you’re building the container, and this is where I wouldn’t have much visibility myself (the pair programming item I mentioned earlier :^ ) ). Perhaps you can audit these a bit. If your system is pretty clean-cut and the default setup (that is not much modification has been made), it may just be a bit of digging into it with the dotnet language maintainers. I ran across a github issue that appears to be similiar to your own (albeit, not exactly the same issue): https://github.com/dotnet/dotnet-docker/issues/1946
I have a few additional resources that can help. We recently published a blog post (5 days ago as of this writing) on getting started with the dotnet 6 runtime for AWS Lambda here: https://aws.amazon.com/blogs/compute/introducing-the-net-6-runtime-for-aws-lambda/
Also within the past hour as of this writing, we had a video tutorial from our Serverless Team providing a few demos of the newly released dotnet 6 runtime: https://www.youtube.com/watch?v=l4_WNjMHDx8
For any further troubleshooting you can check out the aws dotnet GitHub page and submit an issue and they may be ran across this type of error before: https://github.com/aws/dotnet
Relevant content
- Accepted Answerasked 2 years ago
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago