containerized-data-importer
containerized-data-importer copied to clipboard
kubevirt
ARM64 Support
We have been releasing nightlies for arm for some time now. Just haven't made an officially supported release with it yet.
When will officially declare release support for KubeVirt on Arm64? Do you have a release plan？ @awels
Thanks for your report. We will update the release script to also generate the ARM manifests and containers.
Thanks for your report. We will update the release script to also generate the ARM manifests and containers.
tks
I'm running into this issue as well:
Unable to find image 'quay.io/kubevirt/kubevirt-cdi-bazel-builder:2303100312-524798ad' locally
2303100312-524798ad: Pulling from kubevirt/kubevirt-cdi-bazel-builder
docker: no matching manifest for linux/arm64/v8 in the manifest list entries.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Is there any update or progress on arm64 architecture? Can I use daily built images as official releases? @awels
We should investigate the kubevirt/kubevirt arm lane to see how testing might work.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
We have periodics building the images but we don't actually have an official arm release. Just need to put this part together and we can consider this done.
Is there anything an external contributor can do to help?
We're quite interested in running KubeVirt on arm64 machines, but have very little experience with bazel so would need guidance.
Would building multi-arch images be an easier step forward for this?
So we do create ARM nightlies. Just haven't hooked up the process into an official release. I just haven't gotten the time to really look into it and make it properly generate an arm container during a release.
There are several ways we could go about this. We could do it in bazel, but we would have to update a bunch of related bazel libraries so that bazel can create the multi arch containers. Or we could have bazel create the different arches in the local container cache, and then use something like buildah to create a multi arch container from that. That would just require some bash scripts. I spend a little bit of time on option one, and it was quite complicated to get that right. So next time I have some time I will explore option 2.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.