qemu: uncaught target signal 11 (Segmentation fault) - core dumped

[raffaelespazzoli]

I get the error message in the title when I try to run:

yum update.

I'm running a fedora 24 as the host, I run:
docker run --rm --privileged multiarch/qemu-user-static:register

before starting the centos container.
I'm using the fedora docker package not the docker.io package.
Here is the printout of docker info :

[rspazzol@localhost origin]$ docker info
Containers: 2
Running: 0
Paused: 0
Stopped: 2
Images: 21
Server Version: 1.10.3
Storage Driver: devicemapper
Pool Name: docker-253:1-2230976-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 5.335 GB
Data Space Total: 107.4 GB
Data Space Available: 34.55 GB
Metadata Space Used: 5.39 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.142 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev or use --storage-opt dm.no_warn_on_loop_devices=true to suppress this warning.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.122 (2016-04-09)
Execution Driver: native-0.2
Logging Driver: journald
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 4.6.7-300.fc24.x86_64
Operating System: Fedora 24 (Workstation Edition)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 0
CPUs: 4
Total Memory: 19.04 GiB
Name: localhost.localdomain
ID: ZITI:QGE4:AX63:Y4HG:QY72:AGBZ:6UGQ:44ZQ:3V7F:FW3P:7LB4:AAGA
Registries: docker.io (secure)

[moul]

I experienced similar issues, from what I understood they are caused by limited features support in QEMU.
For the CentOS family I don't know, but in Ubuntu, I had numerous similar errors with Ubuntu 14.04, and now I'm fine with Ubuntu 16.04

---

As a workaround, you can try to run the failing commands on real ARM hardware.

Then you can push the generated Docker image and continue to work using QEMU for "working" Docker RUN commands

[junaruga]

I am similar report about this issue.
https://stackoverflow.com/questions/54735030/qemu-arm-qemu-uncaught-target-signal-11-segmentation-fault-core-dumped

Today I tried it with latest qemu 4.0.0. But still same error.

$ docker run --rm --privileged multiarch/qemu-user-static:register --reset

$ docker run --rm -t multiarch/centos:7.6-armhfp-iso uname -a
Linux 51248b9602e1 5.0.10-300.fc30.x86_64 #1 SMP Tue Apr 30 16:22:12 UTC 2019 armv7l armv7l armv7l GNU/Linux

$ docker run --rm -t multiarch/centos:7.6-armhfp-iso yum -y update
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
^C

[mikesart]

I'm running into this also. Wrote docker scripts to build SDL2 x86_64, Aarch64, and Armhf with multiarch centos 7, and everything works great except armhf yum is crashing. I'm using qemu v3.1.0 on Debian Buster. Bummed to see this is still broken with the latest qemu. Guess I'll need to track down a Raspberry Pi and build on native hardware.

[jjhelmus]

I was running the same segmentation fault issue with the armhfp image and found that specifying the yum and rpm architecture explicitly got yum working:

echo "armhfp" > /etc/yum/vars/basearch 
echo "armv7hl" > /etc/yum/vars/arch
echo "armv7hl-redhat-linux-gpu" > /etc/rpm/platform

[Valiento]

@jjhelmus thank you so much, it works!