-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lambda layer does not work #30
Comments
Yes, I am using the latest version in production. |
I used the test file you provided in this repository. |
I can confirm that it does not actually work. My tests were running against an old version. I thought it might be the missing x265 which I added in 4.1.0 but it still doesn't work. No idea why. vips 8.15.2 is compiled with libheif
|
The compilation itself works; you can test it e.g. inside the build docker container without issues (both sharp and vips). I assume the issue is with the packaging. If I have more time I'll investigate further. |
@zoellner I think the issue for you might be the same as in my script; the preset for libheif has to be changed during the compilation to "release-noplugins" in order to create a static build. You can also have a look at my code for the sharp-heif layer here: https://github.com/Dobe-Solutions/sharp-heif-lambda-layer |
Thank you. will give that a try |
Had to make a few more tweaks but seems to work now. Thanks again for debugging |
Hi there,
I tried out the Lambda layer following your build script but I am getting an error running the example code of this repository:
The steps I did for the build were:
sam build --use-container --build-image public.ecr.aws/sam/build-nodejs20.x:latest
- zip the build output and load it into a Lambda layer; create a Lambda function with the content of the examples layer and test it.I have a very similar build script for building a Lambda layer which also doesn't work for me (see ticket lovell/sharp#4081).
Do you was able to test the Lambda layer with the latest versions?
The text was updated successfully, but these errors were encountered: