Fix: IPFS Kubo could use unlimited resources

[hoh]

In observations on multiple CRNs and CCNs,
it seems to use around 700-900 MB.

Limiting the resources to 2GB and hard to 4GB
seems therefore sensible.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.26%. Comparing base (f09bdd2) to head (14c4c6c).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #768   +/-   ##
=======================================
  Coverage   63.26%   63.26%           
=======================================
  Files          77       77           
  Lines        6855     6855           
  Branches      576      576           
=======================================
  Hits         4337     4337           
  Misses       2329     2329           
  Partials      189      189           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Psycojoker]

LGTM

[olethanh]

According to the Kubo doc we should also set GOMEMLIMIT env var to avoid having it OOM killed

To set memory limit for the entire Kubo process, use GOMEMLIMIT environment variable which all Go programs recognize, and then set Swarm.ResourceMgr.MaxMemory to less than your custom GOMEMLIMIT.

[olethanh]

forgot link to Kubo doc here : https://github.com/ipfs/kubo/blob/master/docs/config.md#swarmresourcemgrmaxmemory

Will add the modification

[hoh]

CI failed due to:

docker: Error response from daemon: toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit.

[olethanh]

failing because of

Job for ipfs.service failed because the control process exited with error code.

See "systemctl status ipfs.service" and "journalctl -xeu ipfs.service" for details.

dpkg: error processing package aleph-vm (--configure):
 installed aleph-vm package post-installation script subprocess returned error exit status 1
Setting up gstreamer1.0-libav:amd64 (1.22.0-2) ...
Setting up qemu-system-gui (1:7.2+dfsg-7+deb12u12) ...
Processing triggers for libc-bin (2.36-9+deb12u9) ...
Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.10+dfsg-1+deb12u1) ...
Errors were encountered while processing:
 aleph-vm
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

[hoh]

This approach does not work with recent versions of Kubo, see https://github.com/aleph-im/aleph-vm/pull/779/files where we use systemd ExecStartPre for that purpose.

[hoh]

Moved into #779