Comment by ~ave on ~sircmpwn/builds.sr.ht
On our own instance we've also had this issue, and it seems like oom-killer was indeed the problem:
[2059133.197720] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=af5093108577c3a42b1f80d9a2e47f09f19dc700a3b3707edc05262a897af6fe,mems_allowed=0,global_oom,task_memcg=/docker/852c3e6b9a045b85fb87c3fb494889cae4fbdc8ea3039e5bcb2d05015f41027b,task=qemu-system-x86,pid=6530,uid=0 [2059133.197861] Out of memory: Killed process 6530 (qemu-system-x86) total-vm:18293492kB, anon-rss:14784824kB, file-rss:0kB, shmem-rss:4kB, UID:0 pgtables:31032kB oom_score_adj:0 [2059134.204457] oom_reaper: reaped process 6530 (qemu-system-x86), now anon-rss:0kB, file-rss:20kB, shmem-rss:4kB
We've bumped up the RAM as a workaround which will hopefully help with this issue.