docs: set 16 GB minimum supported RAM
This commit is contained in:
@@ -143,7 +143,7 @@ Build host notes:
|
||||
- The live-build workdir under `dist/` is disposable; source files under `iso/builder/` stay clean.
|
||||
- Container build requires `--privileged` because `live-build` uses mounts/chroots/loop devices during ISO assembly.
|
||||
- On macOS / Docker Desktop, the builder still must run as `linux/amd64` so the shipped ISO binaries remain `amd64`.
|
||||
- Operators must provision enough RAM to hold the full compressed live medium plus normal runtime overhead, because `toram` copies the entire read-only ISO payload into memory before the system reaches steady state.
|
||||
- Supported systems have at least 16 GB of installed RAM. This provides room for the full compressed live medium plus normal runtime overhead because `toram` copies the entire read-only ISO payload into memory before the system reaches steady state. A mid-copy failure must not be classified as low RAM without direct `ENOSPC`, OOM, or tmpfs-limit evidence.
|
||||
|
||||
## Post-boot smoke test
|
||||
|
||||
|
||||
@@ -91,7 +91,7 @@ Fills gaps where Redfish/logpile is blind:
|
||||
- Live-ISO-only responsibilities stay in `iso/` integration code
|
||||
- Live ISO launches the Go CLI with `--runtime livecd`
|
||||
- Local/manual runs use `--runtime auto` or `--runtime local`
|
||||
- Live ISO targets must have enough RAM for the full compressed live medium plus runtime working set because the boot medium is copied into memory at startup
|
||||
- Live ISO targets have a supported minimum of 16 GB installed RAM, enough for the full compressed live medium plus runtime working set; mid-copy failures require direct evidence before being classified as memory exhaustion
|
||||
|
||||
## Key paths
|
||||
|
||||
|
||||
Reference in New Issue
Block a user