The Hermes Agent container backend resources are insufficient, and the manifestations are usually installation dependencies being killed, the build fails, the disk is full, and the test is exited halfway through. The solution direction is to adjust terminal.container_cpu, terminal.container_memory, and terminal.container_disk, rather than changing the model.
Which backends will be affected
Container backends such as Docker, Singularity/Apptainer, Modal, and Daytona can be affected by resource constraints. The official tooling documentation provides uniform container resource configuration: CPU cores, memory MB, disk MB, and whether the file system is persisted.
How to adjust
- Insufficient memory: Raise the
terminal.container_memory, such as from the default to a size that is better suited to the build. - Insufficient disk: Improve
terminal.container_disk, especially for projects with a lot of Node, Python, and model dependencies. - Slow concurrent compilation: Improves
terminal.container_cpu. - Don't want to reinstall dependencies every time: confirm that
container_persistentis true.
Troubleshoot and ask Hermes to run df -h, free -m, nproc first. Resource problems should be judged by system indicators, not just by looking at the model summary.
