[Bug]: Segmentation fault (core dumped) when run on arm linux
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.8k
- Forks
- 491
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Preconditions (Any important steps we need to know)
[root@controller-node-1 ~]# lscpu
架构: aarch64
CPU 运行模式: 64-bit
字节序: Little Endian
CPU: 4
在线 CPU 列表: 0-3
每个核的线程数: 1
每个座的核数: 1
座: 4
NUMA 节点: 1
厂商 ID: HiSilicon
BIOS Vendor ID: QEMU
型号: 0
型号名称: Kunpeng-920
BIOS Model name: virt-9.0
步进: 0x1
Steps to reproduce (How to reproduce what you found step by step)
[root@controller-node-1 ~]# nerdctl run -it --name redisinsight -p 5540:5540 --entrypoint /bin/sh docker.m.daocloud.io/redislabs/redisinsight:2.52.0
/usr/src/app $
/usr/src/app $
/usr/src/app $ ./docker-entry.sh node redisinsight/api/dist/src/main
Running docker-entry.sh
Segmentation fault (core dumped)
Actual behavior (A short description of what you found)
Segmentation fault (core dumped)
Expected behavior (A short description of what you expected to find)
The container run witout error.
Screenshots (Paste or drag-and-drop a screenshot or a link to a recording)
Additional context (Operating system, version of Redis Insight, Redis database version, Redis module version, database type, connection type, logs, or any other information)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure on the aarch64 Kunpeng-920 environment using the documented nerdctl command, then run docker-entry.sh with node redisinsight/api/dist/src/main. Start by examining that entry point and the container runtime behavior around the segmentation fault. Done means the Redis Insight container starts without a segmentation fault on ARM Linux.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, node.js
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100