Hi everyone,

We are testing a local background service running on client laptops. During peak context processing, memory spikes can risk pushing the host OS into swap death.

We are configuring container resource limits (--memory, --memory-swap, cgroups v2) to isolate the local execution daemon from the rest of the host system.

For those deploying background containers on desktop client endpoints: what memory overhead buffer do you leave for the host OS to prevent hard freezes when a container hits its hard limit?

Context: Architectural query regarding container limits on client endpoints.