-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Crash on debian, docker (probably AVX issue) #431
Comments
Yes, this is probably an issue with AVX instructions set. Here is a similar issue imgproxy/imgproxy#856. Could you try to install it without docker, with npm:
to see, if it can work |
This is most likely caused by sharp, lovell/sharp#2723 |
Didn't help. It installed fine, but running |
Could you test if sharp@0.31.0 does work with this script mkdir mediatracker-test
cd mediatracker-test
npm init -y
npm i sharp@0.31.0
node -e "const sharp = require('sharp'); sharp({ create: { width: 48, height: 48, channels: 4, background: { r: 255, g: 0, b: 0, alpha: 0.5 } } }) .png() .toBuffer()" If not, then hopefully build libvips from source code should resolve this issue |
It's the same
|
Could you try building libvips from source,
|
doesn't throw an error now
should there be no output? |
No, building libvips from source solves this issue. I am now working on a Dockerfile |
Thanks! It's all working on 0.1.0-beta.35 (had to build myself). No more Should I close the issue, or is there more to do? |
Could you also try prebuild image from |
It's working just as well with the prebuilt one. Logs below
|
That's great :) |
I'm having trouble getting Mediatracker's docker container to work on my machine. Using latest doesn't provide any logs. Unstable (and the self built one) give
llegal instruction
and exit with code 132.System info:
CPU: Core 2 Duo - E6750
OS: 5.10.120-1 (2022-06-09)
logs (unstable / self built):
(looping due to
restart: unless-stopped
)compose:
The text was updated successfully, but these errors were encountered: