Segmentation fault on ARM64
See original GitHub issueChecklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latest
docker image? Yes - Are you sure you’re not using someone else’s docker image? Yes
- Have you searched for similar issues (both open and closed)? Yes
Describe the bug I got a segmentation fault when I try to run the container using the docker-compose.yml from here: https://nginxproxymanager.com/setup/#running-on-raspberry-pi-arm-devices .
Same error with NPM tags 2.9.3, 2.8.0, github-develop
Here is the log:
app_1 | [5/26/2021] [6:06:36 PM] [Global ] › ℹ info Generating MySQL db configuration from environment variables
app_1 | [5/26/2021] [6:06:36 PM] [Global ] › ℹ info Wrote db configuration to config file: ./config/production.json
app_1 | [5/26/2021] [6:06:38 PM] [Migrate ] › ℹ info Current database version: none
app_1 | ./run: line 18: 229 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1 | [5/26/2021] [6:06:40 PM] [Migrate ] › ℹ info Current database version: none
app_1 | ./run: line 18: 271 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1 | [5/26/2021] [6:06:41 PM] [Migrate ] › ℹ info Current database version: none
app_1 | ./run: line 18: 294 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1 | [5/26/2021] [6:06:43 PM] [Migrate ] › ℹ info Current database version: none
app_1 | ./run: line 18: 307 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1 | [5/26/2021] [6:06:45 PM] [Migrate ] › ℹ info Current database version: none
app_1 | ./run: line 18: 320 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
Operating System
- Oracle Linux 8: Image: Oracle-Linux-Cloud-Developer-8.3-aarch64-2021.05.12-1
- Podman / Docker -> same error
$ lscpu
Architecture: aarch64
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: ARM
Model: 1
Stepping: r3p1
BogoMIPS: 50.00
NUMA node0 CPU(s): 0,1
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Segmentation fault (core dumped) at runtime in ARM64 self ...
Segmentation fault (core dumped) when running a .NET Core self-contained, single file application within ARM64 container mcr.microsoft.com/ ...
Read more >Segmentation fault in a pod running on Graviton ARM64
I try to do a simple apt-get install curl on a pod running on ARM64 (Graviton), I get a Segmentation fault (core dumped)....
Read more >qemu-user-static: lli-13/arm64 causes segfault on amd64 host
on an amd64 host in in arm64 chroot running under qemu-user-static, I observed some segmentation fault while building pocl against llvm-13
Read more >Re: Segfault in pahole 1.18 when building kernel 5.9.1 for arm64
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as...
Read more >What to do about segmentation faults - Arm Developer
There are many possible causes of segmentation faults. They might be caused by problems with your application. You must also ensure that: When...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There was a bit of a delay, upstream docker image changes caused builds to fail for a while.
You can now verify this is fixed with this image:
it’s using node v16.6.2 currently.
If it’s all working please close this issue 😃
Alrighty, I’ll update the base node version to 16 and see what breaks