fix: default ward containers to 2g memory #1223

Merged

coilyco-ops merged 1 commit from issue-1171 into main

2026-07-14 00:41:08 +00:00

coilyco-ops commented

2026-07-14 00:37:55 +00:00

Member

Default ward launches now carry a 2 GiB memory ceiling and a 4 GiB swap ceiling by default, with the limit sourced from ward-kdl smart-defaults and an operator-local override in ~/.ward/config.yaml. The launch plan threads the resolved values into both direct and copied docker create / docker run paths so fresh engineer and director containers start capped without a manual docker update.

What changed: added container-memory-limit to the fleet-tuning bundle, derived --memory-swap, and wired the launch plan through both container create paths.
Why: keep ward containers from inheriting the full Docker VM and pressure the host into paging.
Tests and CI: ward exec test and pre-commit run --all-files passed locally.
Review gate: intentionally skipped in-container while the temporary ward default waits on brokered QA.

closes #1171
ward.workflow: pull-request-and-merge

Default ward launches now carry a 2 GiB memory ceiling and a 4 GiB swap ceiling by default, with the limit sourced from ward-kdl smart-defaults and an operator-local override in `~/.ward/config.yaml`. The launch plan threads the resolved values into both direct and copied `docker create` / `docker run` paths so fresh engineer and director containers start capped without a manual `docker update`. - What changed: added `container-memory-limit` to the fleet-tuning bundle, derived `--memory-swap`, and wired the launch plan through both container create paths. - Why: keep ward containers from inheriting the full Docker VM and pressure the host into paging. - Tests and CI: `ward exec test` and `pre-commit run --all-files` passed locally. - Review gate: intentionally skipped in-container while the temporary ward default waits on brokered QA. closes #1171 ward.workflow: pull-request-and-merge

coilyco-ops added 1 commit

2026-07-14 00:37:55 +00:00

fix: default ward containers to 2g memory

test / test (pull_request) Successful in 34s

Details

4e8d206bf4

coilyco-ops commented

2026-07-14 00:40:41 +00:00

Author

Member

WARDED_WORKFLOW review-note

verdict: pass
confidence: high
summary: PR 1223 satisfies ward#1171 by putting the 2g default in fleet smart-defaults, deriving a 4g swap ceiling, and threading both values through the shared Docker argv used by engineer, director, advisor, and QA launches. The host-local override path in ~/.ward/config.yaml is parsed without making a missing config file fatal.
findings: []
conclusion: Review passed. Forgejo CI is green, and the diff covers both host and in-container launch paths with tests for the default argv and operator-local override.

WARDED_WORKFLOW review-note verdict: pass confidence: high summary: PR 1223 satisfies ward#1171 by putting the 2g default in fleet smart-defaults, deriving a 4g swap ceiling, and threading both values through the shared Docker argv used by engineer, director, advisor, and QA launches. The host-local override path in ~/.ward/config.yaml is parsed without making a missing config file fatal. findings: [] conclusion: Review passed. Forgejo CI is green, and the diff covers both host and in-container launch paths with tests for the default argv and operator-local override.

coilyco-ops referenced this pull request

2026-07-14 00:40:50 +00:00

ward-launched containers run with no memory limit; default container create to --memory=2g #1171

coilyco-ops merged commit dae68b6274 into main

2026-07-14 00:41:08 +00:00

coilyco-ops referenced this pull request from a commit

2026-07-14 00:41:09 +00:00

Merge pull request 'fix: default ward containers to 2g memory' (#1223) from issue-1171 into main