big-data-europe/docker-hive

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

ruchit6370 opened this issue · 8 comments

ruchit6370 commented

I try to run docker-hive using following commands, but I'm not able to start hive server, and getting some segmentation fault error.

$ docker-compose up -d
Docker Compose is now in the Docker CLI, try `docker compose up`

Recreating docker-hive_datanode_1                  ... done
Recreating docker-hive_hive-server_1               ... done
Recreating docker-hive_namenode_1                  ... done
Recreating docker-hive_hive-metastore-postgresql_1 ... done
Recreating docker-hive_presto-coordinator_1        ... done
Recreating docker-hive_hive-metastore_1            ... done
$ docker-compose exec hive-server bash
root@2c02ebc72a4d:/opt# /opt/hive/bin/beeline -u jdbc:hive2://localhost:10000
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault

I see many people have faced similar issue. In this comment, it is suggested to supply arm64 or multi-arch image. Is this done, or possible to do in future? I'm facing this issue on Mac M1.

Durgajo commented

Facing the same issue on Mac M1

NanoBjorn commented

same here

pablos87 commented

Facing the same issue on Mac M1

toby1991 commented

Facing the same issue on Mac M1

rinat-akhmetov commented

so am I.
Step to reproduce
docker run --platform linux/amd64 --rm -p8000:8000 -p8001:8001 -p8002:8002 nvcr.io/nvidia/tritonserver:21.08-py3 tritonserver --model-repository=/models

Melvandito commented

facing the same issue

status: PENDING ASSETS ii: Waiting SIGSEGV: segmentation violation PC=0x0 m=7 sigcode=0 qemu: uncaught target signal 11 (Segmentation fault) - core dumpe

michaeljwiebe commented

same issue, mac M1. adding platform: "linux/x86_64" to one of the images in my docker-compose.yml file seems to have fixed this

kelsi-kw commented

Same issue.
qemu: uncaught target signal 11 (Segmentation fault) - core dumpe