Conversation
Co-authored by: nijincheng@iscas.ac.cn; Signed-off-by: ffgan <sudoemt@gmail.com>
|
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? |
|
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. |
|
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. |
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. |
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:
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:
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:
Otehr Info
Co-authored by: nijincheng@iscas.ac.cn;