adityabagchi24andGitHub a58c5fe66c Adjust overcommit and max_map_count vm defaults in guest VMs (#2055) ...

Each container runs in its own guest VM sized to
`--memory` with no swap, so the guest kernel's
stock `vm` sysctl defaults are hit far too easily:

- `vm.overcommit_memory=0` (heuristic overcommit)
  rejects an oversized `mmap()` upfront whenever the
  reservation exceeds the small, swap-less VM's free
  RAM — even if the memory is never touched —
  returning `ENOMEM`.
- `vm.max_map_count=65530` caps per-process
  mapping count, which mapping-heavy applications
  (e.g. Elasticsearch, many JVMs) can exceed.

2026-08-02 15:33:52 -07:00

..

Client

Reorganize runtime targets for scalable plugin support (#1577)

2026-05-20 12:57:10 -07:00

Server

Adjust overcommit and max_map_count vm defaults in guest VMs (#2055)

2026-08-02 15:33:52 -07:00