-
-
Notifications
You must be signed in to change notification settings - Fork 7k
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
arm64 image doesn't build libvips #33164
Comments
This is weird and probably related to your setup (lack of memory / disk space?), as it builds correctly on ARM64 on our CI (see https://github.com/mastodon/mastodon/actions/runs/12151857539/job/33887208269 where it builds AMD64+ARM64) |
I see this occasionally when building locally and it usually has to do with stale Docker build cache.
|
I think mine usually fails on the amd64 compile because I'm doing it on an M3 Max (Arm) system. @richarvey are you by chance doing the arm compile on Intel/AMD? As I understand it the CI pipeline does the builds on native hardware for each and then combines them together. I wonder if there is something in the Dockerfile we could do better here, or if this is just an artifact of cross compiling. |
So if i compile this on m apple M2 no issues. if i Use my intel debian laptop it fails. I tried running:
Unfortunately it didn't help. The last successful build was 4.3.0 as i build 4.3.1 on the mac. |
What versions of Docker and buildx? |
To add to the fact it's probably a cross compile issue I just tried this on an AWS Graviton m4a and the amd64 build failed.
buildx
and buildkit:
|
Steps to reproduce the problem
Expected behaviour
Docker image should have been built
Actual behaviour
segfault whilst building libvips stops build process
Detailed description
when trying to build the docker images the amd64 build works fine but when compiling libvips on arm64 meson/ninja seg faults. detailed output below:
I attempted to fix this with later versions of libvips but had no luck. I assume it may be meson that is the issue, but I'm unfamiliure with this so I may be wrong.
Mastodon instance
mastodon.squarecows.com
Mastodon version
v4.3.2
Environment
Everything else is standard in the Dockerfile
Technical details
I tried bumping the libvips version to 8.15.4, 8.15.5 and 8.16.0 to see if it was a libvips issue but these failed also. I also noticed that mastodon v4.3.1 successfully built libvips 8.15.3 (8.15.2 also fails)
I believe this is the critical part of the log which is included in the details above
The text was updated successfully, but these errors were encountered: