Node 18.7.0 / Alpine3.16 doesn't start on Raspberry Pi 3B (armv7)

[Krystex]

Environment

• Platform: Raspberry Pi 3B (armv7)
• Docker Version: 20.10.17, build 100c701
• Node.js Version: 18.7.0
• Image Tag: 18.7.0-alpine3.16

Expected Behavior

Node should start without problems.

Current Behavior

Crash on starting "node" binary.

Possible Solution

Steps to Reproduce

docker run --rm node:18.7.0-alpine3.16
# or
docker run --rm -it node:18.7.0-alpine3.16 node

Output:

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7ee2458c

Additional Information

Image node:18-slim works as expected.

Coredump is appended to this issue.

My procinfo

$ cat /proc/cpuinfo
processor	: 0
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 1
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 2
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 3
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

Hardware	: BCM2835
Revision	: a02082
Serial		: 00000000393d37bc
Model		: Raspberry Pi 3 Model B Rev 1.2

core.gz

[Krystex]

So the problem seems to be caused by the alpine image, I can't even ping some host:

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: clock_gettime(MONOTONIC) failed

EDIT: the problem was an buggy, outdated version of libseccomp, which is a common issue with Debian Buster. I fixed it with these instructions