Build process keeps getting killed in Docker

[fnick851]

And it kills the process without showing a reason.

I do notice the CPU usage is high but that's normal I think for Node.

Does anyone has some ideas - what might cause this?
I increased memory and CPU for the container so I don't think it is running out of memory or CPU.
It might be some Linux configuration?

Thanks!

[DanLeininger]

@fnick851 I'm running into this too, did you ever figure out what was killing the build?

[fnick851]

So this was in a Docker container. And we eventually think the reason is still memory. We increased the resources for the container and it seems like the issue is gone now.

I suggest experimenting with allocating more resources to the environment you use. This is likely not an issue with the framework itself.

[d-cs]

I'm getting this when running on M2 processor trying to build a linux/amd64 container

[bloodykheeng]

try to increase your swap memory
for me my issue was that i couldnt npm run build on linux server
out of the blue the terminal was giving me message killed

after some research i found out that my swap memory was 500mb and i extended it to 1gb so the build ran well now
my server was 4gb

to check for swap
cd into root
then type

free

that will show u the available swap memory

the commands below will increase it to 1gb

  sudo /bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024
  sudo /sbin/mkswap /var/swap.1
  sudo /sbin/swapon /var/swap.1