retoor
af080fe68e
- Approval: re-prompt unknown answers (max 3), shell-only affirmative guidance recovery; destructive actions stay strict - GoalVerifier subagent with strict JSON verdicts, bounded follow-up rounds, nonzero exit plus open turn on unverified one-shots - Retrieval eval (Hit@K/MRR/nDCG/Context Precision), FTS cascade with title weighting, query/read event logging, --eval-retrieval CLI - Supervisor caps (8 parallel, 64 records) and scheduler hardening (4 fires/tick, per-schedule lease, stated misfire policy) - Sandbox box resource trio: 2g/2.0/256 at create, best-effort update for existing boxes, rm -f recovery pointer - Research archive: 12 subjects, 667 sources, 27 conclusions; suites 979 + 16 green
29 lines
1.0 KiB
Markdown
29 lines
1.0 KiB
Markdown
# Changing resource limits on a running Docker container
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Institute | Molodetz Institute — Research & Retrieval Division |
|
|
| Subject | sandbox-resource-caps |
|
|
| Document type | Source Citation Card |
|
|
| Tier | 2 |
|
|
| Source title | Changing resource limits on a running Docker container |
|
|
| Source URL | https://stackoverflow.com/questions/35146613/changing-resource-limits-on-a-running-docker-container |
|
|
| Source type | other |
|
|
| Date researched | 2026-10-18 |
|
|
| Researched by | tai (agent), model: Muse Spark, on behalf of retoor |
|
|
| Research method | Search aggregator result listing (not independently opened or quoted) |
|
|
| Confidence | Not independently verified |
|
|
| Status | Active |
|
|
|
|
## Why it's here
|
|
|
|
Surfaced by the update-limits search; the snippet indicates some limits apply live via update while others need recreation. The exact split comes from the vendor docs; this only corroborates the split exists.
|
|
|
|
## Changelog
|
|
|
|
| Date | Change |
|
|
|---|---|
|
|
| 2026-10-18 | Logged as consulted-but-not-analyzed. |
|