Skip to content

Comments

Build riscv64 image#327

Draft
ffgan wants to merge 1 commit intokubevirt:mainfrom
ffgan:build-rv64-image
Draft

Build riscv64 image#327
ffgan wants to merge 1 commit intokubevirt:mainfrom
ffgan:build-rv64-image

Conversation

@ffgan
Copy link

@ffgan ffgan commented Nov 13, 2025

What this PR does / why we need it:

I'm currently working on adding riscv64 support for kubevirt, as detailed in kubevirt/containerized-data-importer#3948. While adding support for CDI, I discovered that this repository needs riscv64 support as well, so I've opened this PR to add riscv64 support.

By checking gcr.io/distroless/base:latest and alpine:latest , we can see the following table:

arch distroless/base alpine
amd64 Y Y
arm64/v8 Y Y
arm/v7 Y Y
s390x Y Y
ppc64le Y Y
riscv64 N Y
386 N Y
arm/v6 N Y

Clearly, Alpine has excellent multi-architecture support. Should we consider switching from distroless/base to Alpine to gain riscv64 support? I believe there shouldn't be any compatibility issues between the two, but I haven't yet found a good approach for testing this image in CI. If I find one, I'll submit the relevant PR promptly.

For now, I've run the CI in my own fork, and the results show everything is working smoothly. Details are as follows:

  1. prom-metrics-linter
  2. Generate a build and push to 'ghpages' branch
  3. Sanity Checks

If you have any questions about the above content, please feel free to contact me directly. I'm happy to answer any related questions.


Release note:

Build riscv64 image

Otehr Info
Co-authored by: nijincheng@iscas.ac.cn;

Co-authored by: nijincheng@iscas.ac.cn;

Signed-off-by: ffgan <sudoemt@gmail.com>
@kubevirt-bot kubevirt-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/XS labels Nov 13, 2025
@sradco
Copy link
Collaborator

sradco commented Dec 1, 2025

@avlitman @nunnatsa can you please have a look?

@nunnatsa
Copy link
Collaborator

nunnatsa commented Dec 8, 2025

Thanks for the PR, @ffgan .

First: is the effort to add riscv64 support is managed by the community? do you have an approved VEP for it?

Also, this image is a build tool. Are you going to run it on a riscv64 machine? or build from another machine for riscv64?

@ffgan
Copy link
Author

ffgan commented Dec 8, 2025

Hi @nunnatsa ,Thank you for your reply.

Regarding VEP, it is still in a relatively early stage at the moment, so we don't have that yet.

Regarding whether to run on riscv64 or on other machines, I may not quite understand what you're referring to.

@ffgan
Copy link
Author

ffgan commented Dec 8, 2025

Regarding this PR, I submitted it because when I was running CDI on riscv64, I discovered that support for this container was missing, so I raised this PR.

@nunnatsa
Copy link
Collaborator

nunnatsa commented Dec 8, 2025

Regarding VEP, it is still in a relatively early stage at the moment, so we don't have that yet.

You should start from VEP... this should be your first step.

@ffgan
Copy link
Author

ffgan commented Dec 8, 2025

You should start from VEP... this should be your first step.

Okay, then I'll prepare for it in the near future and try to apply for VEP as early as possible.

@ffgan
Copy link
Author

ffgan commented Jan 16, 2026

Hi @nunnatsa .

I've already started a VEP, welcome to check it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants