RISC-V buildah image

[MarekPikula]

Hi, I use buildah OCI image in ci-multiplatform project, and I would love to use native RISC-V runners provided by Cloud-V (https://cloud-v.co/gitlab-riscv-runner) to run the image build. The issue is that currently buildah base image is not built for RISC-V (riscv64). What would need to happen to start building upstream RISC-V images?

[nalind]

This is probably something to be tracked in the https://github.com/containers/image_build/ repository.
Since the image we build there uses "registry.fedoraproject.org/fedora:latest" as its base, we'd need that to be built for the target arch. The images install buildah using the Fedora package, so builds of the "stable" and "testing" images would need to be able to find the package in the default repositories available in those images (Fedora's release+updates, or release+updates+updates-testing repositories), and the build for the "upstream" image would need it to be available in the https://copr.fedorainfracloud.org/coprs/rhcontainerbot/podman-next/ repository.

[MarekPikula]

Thanks for clarification. Am I correct that until there are no official RISC-V OCI images for Fedora, it is fairly unlikely to have pre-built images of Buildah?

[nalind]

I'd say that's a reasonable expectation, yes.

[MarekPikula]

Ok, that's good to know. Are you aware of the progress of the official support for RISC-V in Fedora, or should I ask the RISC-V WG directly?

[nalind]

It's not something I'm keeping an eye on, so I'd also end up having to ask them.

[MarekPikula]

All right, I contacted the RISC-V community in Fedora, and although they have OCI images pre-built, they won't be official any time soon. For Fedora to accept RISC-V as a primary architecture, there would need to be proper server hardware available on the market, which won't happen any time soon.
For the time being, I'll build upon Debian base, as Buildah is available there no problem, and RISC-V is officially supported.