Spikes from node let Docker crash

I’m running Alpine 3.23.2 in a VM and the command node ./dist/main.js is freezing my system and crashes Docker.
Even on a fresh install of Nextcloud without any volumes. I can confirm that it is from Nextcloud AIO since it doens’t exist without running the Mastercontainer.

image

I have `vm.overcommit_memory = 1` in my kernel activated. However it also happens without it. Memory in general is enough available and I have nothing running besides Collabora.

docker-compose.yml

services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:beta
    init: true
    restart: always
    container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work
      - /var/run/docker.sock:/var/run/docker.sock:ro
#      - /dockerVolumes/NextcloudAIO:/mnt/ncdata
    ports:
      - 33333:8080 # This port will be used for the installer website
    environment:
#      - DOCKER_API_VERSION=1.44
      - APACHE_PORT=11000 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      - APACHE_IP_BINDING=${IP} # Should be set when running behind a web server or reverse proxy (like Apache, Nginx and else) that is running on the same host. See https://github.com/nextcloud/all-in-one/bl>
#      - NEXTCLOUD_ADDITIONAL_APKS=imagemagick
#      - NEXTCLOUD_ADDITIONAL_PHP_EXTENSIONS=imagick
      - NEXTCLOUD_MEMORY_LIMIT=512M
      - NEXTCLOUD_ENABLE_DRI_DEVICE=true
 #     - NEXTCLOUD_DATADIR=/dockerVolumes/NextcloudAIO
      - COLLABORA_SECCOMP_DISABLED=true
      - BORG_RETENTION_POLICY="--keep-within=7d --keep-weekly=2 --keep-monthly=1 --keep-yearly=1"
    networks:
      - proxied

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer # This line is not allowed to be changed as otherwise the built-in backup solution will not work

Anybody got an idea?
Thanks for your help!

I can’t even think of a reason why node would run like that outside of a dev environment.

Plus dist/main.js is a browser asset.

1 Like

You are indeed right!

I have another container running which makes use of this process.
I traced it down using strace . For whatever reason though my system did crash whenever I boot up nextcloud while it was running.

I continue to investigate this further and might ask for support at the forum of that software.

Okay seems Like it’s not related to just this process but nextcloud / docker do still crash even without the suspected service running.

Before it’s crashing the mastercontainer shows Something about child Prozesses.