Better diagnostics for "no space left on device" error when building images

[ggiguash]

Occasionally, we see the following error when building MicroShift images. The error usually goes away when the same job is rerun. We need to provide more diagnostics in the log collection phase on failure to also include the following commands:

sudo fdisk -l
sudo df -h

See this run for an example of such a failure.

sudo podman build \
        -t "microshift-okd-builder" \
        --ulimit nofile=524288:524288 \
        --build-arg USHIFT_BRANCH="release-4.19" \
        --build-arg OKD_VERSION_TAG="4.19.0-okd-scos.19" \
        -f packaging/microshift-builder.Containerfile .
STEP 1/31: FROM quay.io/centos-bootc/centos-bootc:stream9
Trying to pull quay.io/centos-bootc/centos-bootc:stream9...
Getting image source signatures
Copying blob sha256:dd2e2f497c1eb26a22012f125c7e9e5d8b0d69f5b4d34488570fa69c067beb3f
...
...
Copying blob sha256:61a345d3d15f962e4d21cb282c4c2f1e47c5a6e1888540128c079aa29f09411a
Error: creating build container: copying system image from manifest list: writing blob: storing blob to file "/var/tmp/container_images_storage1881483067/5": write /var/tmp/container_images_storage1881483067/5: no space left on device
make: *** [Makefile:51: rpm] Error 125