Repository navigation
Cannot use node on Raspberry Pi Ubuntu #33244
Description
Activity
Seems to be related to some other issue in aarch64 kernel:
https://bugzilla.redhat.com/show_bug.cgi?id=1813089I guess if it’s a setrlimit thing then that makes sense since node does that pretty early. Not sure if this is something we can deal with here unless something specific to our code or build process can be shown. Likely to be something that intersects with @bnoordhuis’ interests and expertise though if he’s intrigued.
Node.js uses getrlimit/setrlimit to get/set the open file descriptor limit but it's non-fatal if those system calls don't work.
@donfrigo Can you check with gdb where
node -e 42crashes exactly?btprints a backtrace.@bnoordhuis
Hope I did this right:root@b9086729348f:/# gdb /usr/local/bin/node -e 42 GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/bin/node...done. (gdb) run Starting program: /usr/local/bin/node warning: Error disabling address space randomization: Operation not permitted [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1". Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x0000ffff92dd2df4 in __GI_abort () at abort.c:89 #2 0x000000000129c9b0 in thread_stack_size () at ../deps/uv/src/unix/thread.c:176 #3 uv_thread_create_ex (arg=0x1d39d860, entry=0xa87ca0 <node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start()::{lambda(void*)#1}::_FUN(void*)>, params=<synthetic pointer>, tid=0x1d39dff0) at ../deps/uv/src/unix/thread.c:236 #4 uv_thread_create (tid=0x1d39dff0, entry=0xa87ca0 <node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start()::{lambda(void*)#1}::_FUN(void*)>, arg=0x1d39d860) at ../deps/uv/src/unix/thread.c:212 #5 0x0000000000a862bc in node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) () #6 0x0000000000a86580 in node::NodePlatform::NodePlatform(int, v8::TracingController*) () #7 0x00000000009f71d0 in node::InitializeOncePerProcess(int, char**) () #8 0x00000000009f7650 in node::Start(int, char**) () #9 0x0000ffff92dc0364 in __libc_start_main (main=0x0, argc=0, argv=0x0, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=<optimized out>) at libc-start.c:291 #10 0x0000000000999f8c in _start () Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb)- added a commit that references this issue
on May 14, 2020 Thanks, that's really helpful! That's libuv trying to look up the stack size through
getrlimit(RLIMIT_STACK). I've opened libuv/libuv#2848 to work around that.Reacted by ofthesun9- added a commit that references this issue
on May 16, 2022 - added a commit that references this issue
on Feb 25, 2025 - added a commit that references this issue
on Jul 23, 2025 - added a commit that references this issue
on Dec 16, 2025
What steps will reproduce the bug?
I am trying to build a dockerfile on my Raspberry Pi 4, running arm64 Ubuntu. The same dockerfile runs fine on my main computer. The dockerfile is as follows:
Upon building this file I get the following error:
The error code of 134 refers to running out of memory on the host, but I have checked both memory and storage and there seems to be plenty of space left. What could be the issue? Thank you!
Additional information
If I run the base image manually and open a terminal, I get the following: