Bib was broken when building remote bootc image

[chunfuwen]

Command 'sudo podman run --rm -it --privileged --pull=newer --security-opt label=type:unconfined_t -v /var/lib/libvirt/images/output:/output -v /var/lib/libvirt/images/config.json:/config.json -v /var/lib/libvirt/images/auth.json:/run/containers/0/auth.json quay.io/centos-bootc/bootc-image-builder:latest --type raw --tls-verify=false --config /config.json quay.io/centos-bootc/centos-bootc:stream9 ' failed. stdout: b'2025/02/10 17:33:50 error: cannot build manifest: could not access container storage, did you forget -v /var/lib/containers/storage:/var/lib/containers/storage? (cannot find "/var/lib/containers/storage/overlay" (missing -v /var/lib/containers/storage:/var/lib/containers/storage mount?)

[mvo5]

Thanks for reporting the issue - this is fallout from #423 where the default got changed to look into the local storage only to support things like bound images (cc to @ondrejbudai if we need a softer deprecation policy here).

[cgwalters]

Maybe what we could do is detect the case when the user has explicitly done a -v /var/lib/libvirt/images/auth.json:/run/containers/0/auth.json (really detect when /run/containers/0/auth.json exists say) and give them a nice error message saying to explicitly do a podman pull first?

[cgwalters]

@chunfuwen to be clear what we expect customers to do (and what I think we should ensure all CI pipelines are doing) is ensuring the relevant containers are in the storage before invoking bootc-image-builder right now, via e.g. podman pull.

[chunfuwen]

I noticed the output has below warning:bootc-image-builder no longer pulls images, make sure to pull it before running bootc-image-builder:
sudo podman pull quay.io/centos-bootc/centos-bootc:stream9

It looks like it align with what we expect customers to do, so close this issue