Segmentation fault signal terminated program CC1 issue while building Multiarch image on x86

Is this a bug report, feature (enhancement) request or question? (leave only one on its own line) Question /kind bug

/kind enhancement

/kind question

Description:

Steps to reproduce the issue:

Describe the results you received:

Describe the results you expected:

Environment: Prod

• QEMU version: (if you can know it): 7.2..0-1
• Container application: Docker/Podman/Singularity (Leave only one) podman Output of docker version, podman version or singularity version

(paste your output here)

gcc: internal compiler error: Segmentation fault signal terminated program cc1

Please submit a full bug report,

with preprocessed source if appropriate.

See file:///usr/share/doc/gcc-10/README.Bugs for instructions.

make[3]: *** [Makefile:1802: Objects/funcobject.o] Error 4

make[3]: *** Waiting for unfinished jobs....

make[3]: Leaving directory '/home/appuser/Python-3.9.13' Additional information optionally:

I also made the same mistake, have you solved it

I also made the same mistake, have you solved it

Nope

This error started for our builds about a week ago. Compiler SEGFAULTs when buildling python via penv (and other downstream build tasks).

This error started for our builds about a week ago. Compiler SEGFAULTs when buildling python via penv (and other downstream build tasks).

Yes, building python is the issue,Were you able to resolve it?

This is probably related to https://github.com/tonistiigi/binfmt/issues/215. See https://github.com/tonistiigi/binfmt/issues/215#issuecomment-2613004741 for more details on the root cause.

I'm also getting segfaults when installing anything that requires libc-bin, e.g. jq

59.71 Processing triggers for libc-bin (2.35-0ubuntu3.8) ...
59.83 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
59.84 Segmentation fault (core dumped)

facing the same mistake. in my situation I found it happens only on i9/xeon cpu, but ok on i7 platform need help

same error, is there any solutions to solve this problem?

facing the same mistake. in my situation I found it happens only on i9/xeon cpu, but ok on i7 platform need help

it seems happening on some extra feature on xeon? like AVX-2 or VT-x?

guys, I found a solution, using https://hub.docker.com/r/linuxserver/qemu-static instead.