-
-
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
sharp@0.33.2 fails to download binary in docker build #4000
Comments
This is the expected behaviour from v0.33.0 onwards. https://sharp.pixelplumbing.com/changelog#v0330---29th-november-2023
Please see #3750 for full details. |
Thank you! May I ask how to properly install
Installing with user app with
I understand this is not direct sharp issue and do not expect it to be touched on sharp level. Only asking for directions, on how any of the projects (user app, |
It looks like you're using pnpm with multiple platforms (I spy a lockfile that was created outside a container being used inside a container) so please see its |
Good smell! There were indeed no binaries installed for the container architecture. Thank you very much! The error in this particular package ( |
Possible install-time or require-time problem
Are you using the latest version of sharp?
sharp
as reported bynpm view sharp dist-tags.latest
.Are you using a supported runtime?
^18.17.0 || ^20.3.0 || >=21.0.0
Are you using a supported package manager and installing optional dependencies?
--include=optional
--no-optional=false
What is the complete error message, including the full stack trace?
There is no error message with 0.33.2, however
node install/check
seems to run as intendedSee: https://github.com/Aareksio/sharp-build-reproduction/actions/runs/7977103003/job/21779222827
Expected output from 0.32.6:
See: https://github.com/Aareksio/sharp-build-reproduction/actions/runs/7977101833/job/21779218608
I have considered it may not print logs, but the execution time (81ms) is too short for any meaningful action.
Reproduction repo:
The text was updated successfully, but these errors were encountered: