-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
ImageMagick7 and "Input file contains unsupported image format" #2864
Comments
What is the output of running the following commands within this container?
|
|
Thank you, it looks like commit 573ed5f might have broken ImageMagick 7 compatibility. I think we need to add |
Cool! I'll take a look at this over the weekend and see if I can get it fixed, thanks for the super quick response. |
v0.29.1 now available, thanks for both reporting and fixing this. |
Hi there. I'm running into an issue which seems very similar to #2303. My goal is to get sharp running with ImageMagick and lots of other tools (libheif, libwebp, etc) on a Docker image destined for AWS Lambda. Everything is working well except for ImageMagick. It's detected during
libvips
installation, and can be used with e.g.vips magickload
, but trying to load a.bmp
or other IM-compatible file with sharp gives "Input file contains unsupported image format". I've created a basic repro of the problem here: https://github.com/paulstraw/sharp-magick-lambdaThanks very much for your help, and your work on sharp. Please let me know if there's any additional information I can provide.
Yep, I've referenced this doc extensively, and it's been very helpful in getting this far.
Yes, there is only one Node installed on the Docker image I'm using.
Yes, sharp
0.29.0
.Yes, although I've also tried without, and installation appears to work successfully either way.
N/A
N/A
Yes. I don't see any errors, and the system libvips is detected.
npm install --verbose sharp
The text was updated successfully, but these errors were encountered: