Skip to content

feat(system_imaging): let an oras image say how much to grow by - #240

Merged
safl merged 5 commits into
mainfrom
oras-disk-grow
Oct 29, 2026
Merged

safl merged 5 commits into
mainfrom
oras-disk-grow

Conversation

@safl

@safl safl commented Oct 29, 2026

Copy link
Copy Markdown
Collaborator

system_imaging.diskimage_from_oras grows a staged image by a size the image names, disk.grow, 8G by default, so AiSIO can stage its guest with the 32G its SPDK build needs instead of with a staging script of its own. A growth other than the default is kept in the stamp, so changing it re-stages. With the registry unreachable, a staged tag is now used only if it was staged from the tag the config names. Bumps to v0.9.69.

Not tested: a real pull and resize; the unit tests stub the registry and qemu-img.

Assisted-by: Claude Code:claude-opus-5-5

safl added 5 commits October 29, 2026 17:30
diskimage_from_oras grew every staged image by 8G, so a guest that
builds large software in place, as AiSIO's builds SPDK, needed its own
staging script to get the room. An image now names its growth as
disk.grow, 8G by default, and a growth other than the default is kept
in the stamp, so changing it re-stages while stamps written before
keep matching.

Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Simon A. F. Lund <os@safl.dk>
Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Simon A. F. Lund <os@safl.dk>
Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Simon A. F. Lund <os@safl.dk>
…s it

With the registry unreachable, a tag-pinned image that was staged was
used whatever tag it was staged from, so a config moved to another tag
while offline ran the old image with only a warning. The reference an
image was staged from is now kept next to it, and an unreachable
registry falls back to the staged image only when that reference is the
one the config names.

Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Simon A. F. Lund <os@safl.dk>
Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Simon A. F. Lund <os@safl.dk>
@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 40913721460

Warning

No base build found for commit ae5b6f2 on main.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 63.383%

Details

  • Patch coverage: 10 of 10 lines across 2 files are fully covered (100%).

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →


Coverage Stats

Coverage Status
Relevant Lines: 3167
Covered Lines: 2063
Line Coverage: 65.14%
Relevant Branches: 1208
Covered Branches: 710
Branch Coverage: 58.77%
Branches in Coverage %: Yes
Coverage Strength: 0.65 hits per line

💛 - Coveralls

@safl
safl merged commit 4c08935 into main Oct 29, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants