[Tracker] Docker build fails on CI for arm64

[ngxson]

Tracker for upstream issue: docker/build-push-action#1309

At the time of writing this issue, this has been failing for the past 3 days: https://github.com/ggml-org/llama.cpp/actions/workflows/docker.yml

It was fixed in #11472 but now the problem came back.

CC @ggerganov @slaren for visibility

[ggerganov]

I noticed that and these failures are actually now caused by a different issue:

https://github.com/ggml-org/llama.cpp/actions/runs/13322407195/job/37209322813#step:8:2252

#11 128.3 Processing triggers for libc-bin (2.35-0ubuntu3.8) ...
#11 128.4 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#11 128.9 Segmentation fault (core dumped)
#11 129.0 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#11 129.7 Segmentation fault (core dumped)
#11 129.7 dpkg: error processing package libc-bin (--configure):
#11 129.7  installed libc-bin package post-installation script subprocess returned error exit status 139

Googling a bit:

tonistiigi/binfmt#240

Edit: nvm, it might be the same issue

[ngxson]

I'm running a CI with tonistiigi/binfmt:qemu-v7.0.0-28 on my fork: https://github.com/ngxson/llama.cpp/actions/runs/13346220830/job/37276975481

Will make a PR if it fixes the issue

[ngxson]

Seems like ARM64 build still fail no matter what we tried, can we move the ARM64 build to a self-hosted runner @ggerganov ?

[ggerganov]

Which one is the failing build now?

[ngxson]

This for example, was yesterday: https://github.com/ggml-org/llama.cpp/actions/runs/14005118034/job/39217964069

And 2 days ago: https://github.com/ggml-org/llama.cpp/actions/runs/13984528655/job/39155834450

Indeed, the annoying thing is that both x64 + arm64 are built on the same workflow, so if arm64 fails, then x64 won't get published. This makes the CPU image tag to lag behind CUDA and other backend, even though x64 build passes

[ggerganov]

I see. Did you find any information what is the cause this time? Maybe it will be resolved soon.

[ngxson]

I have been applying many suggestions from tonistiigi/binfmt#215 but the issue still come back after a while.

On second thought, I think we could try using arm64 hosted runner to get rid of the emulation. What I don't know is that will ARM extensions like VFP or NEON be enabled in build time.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.