diff options
| -rwxr-xr-x | image-builder/build-full-image.sh | 10 | ||||
| -rwxr-xr-x | image-builder/build-sbo-testbuild.sh | 7 |
2 files changed, 17 insertions, 0 deletions
diff --git a/image-builder/build-full-image.sh b/image-builder/build-full-image.sh index 6f88db7..6ca0288 100755 --- a/image-builder/build-full-image.sh +++ b/image-builder/build-full-image.sh @@ -225,6 +225,16 @@ DOCKERFILE return 1 fi + # The rebuild left the previous image untagged but still resident, ~33G for + # -current. Waiting for a daily prune means the next variant builds on top + # of that dead weight: exporting a 33G image needs its own size again in + # transient space, and the volume was short enough that the -current build + # failed six nights running with "no space left on device". Drop it here, + # while the tag we just pushed is the only one referencing its layers. + # Best-effort: a failed prune costs space, not correctness. + _log " Pruning superseded images..." + docker image prune -f >/dev/null 2>&1 || _warn " image prune failed (ignored)" + _log "=== Done: ${FULL_TAG} ===" } diff --git a/image-builder/build-sbo-testbuild.sh b/image-builder/build-sbo-testbuild.sh index 8d08a03..d40ccb1 100755 --- a/image-builder/build-sbo-testbuild.sh +++ b/image-builder/build-sbo-testbuild.sh @@ -135,6 +135,13 @@ DOCKERFILE _warn " push failed for ${TB_TAG}." return 1 fi + + # Drop the image this rebuild superseded rather than leaving it resident + # until a daily prune; see the same step in build-full-image.sh for why + # that mattered. Best-effort: a failed prune costs space, not correctness. + _log " Pruning superseded images..." + docker image prune -f >/dev/null 2>&1 || _warn " image prune failed (ignored)" + _log "=== Done: ${TB_TAG} ===" } |