Closed tschaffter closed 12 months ago
There is almost no space left on the EC2 instance:
vscode@7047b27f8ebb:/workspaces/sage-monorepo$ df -h
Filesystem Size Used Avail Use% Mounted on
overlay 80G 74G 6.1G 93% /
Removing all Docker artifacts in the dev container does not free as much as expected:
vscode@7047b27f8ebb:/workspaces/sage-monorepo$ df -h
Filesystem Size Used Avail Use% Mounted on
overlay 80G 58G 23G 72% /
Removing all the images on the host saves 23G:
[ec2-user@ip-10-41-30-105 sage-monorepo]$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 596K 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/nvme0n1p1 80G 37G 44G 46% /
tmpfs 3.2G 0 3.2G 0% /run/user/1000
After making some space, the OC stack started successfully, including the Elasticsearch nodes.
Is there an existing issue for this?
What product(s) are you seeing the problem on?
OpenChallenges
Current behavior
openchallenges-build-images
nx serve-detach openchallenges-organization-service
The three ES instances fail to start. The 2nd and 3rd nodes fail because the first node fails. The logs of the first node end with:
Expected behavior
No response
Anything else?
Experienced when working on #2079
Commit ID
No response
Are you developing inside the dev container?
Code of Conduct