It is probably not actually running out of memory. Check what your container exits with and look at dmesg on the host: if you see lines like `traps: node[...] trap invalid opcode ... in skia.linux-x64-musl.node` and an exit code of 132, that is SIGILL, an illegal CPU instruction, not an OOM kill. Th…
It is probably not actually running out of memory. Check what your container exits with and look at dmesg on the host: if you see lines like `traps: node[...] trap invalid opcode ... in skia.linux-x64-musl.node` and an exit code of 132, that is SIGILL, an illegal CPU instruction, not an OOM kill. Th…