You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that the RapidFort platform already supports ARM64 for non-community images, it would be highly advantageous to extend ARM64 compatibility to the community containers. With the growing adoption of ARM-based architectures—exemplified by M-series Macs and Snapdragon-powered Windows laptops—supporting an ARM64 variant for community images is becoming increasingly essential.
Furthermore, I see no evident technical barrier preventing the release of ARM64 containers. There should be no reason to continue releasing only x86/64 containers when the RapidFort platform already supports ARM64, as this would ensure broader device compatibility and inclusivity for emerging ARM-powered platforms.
What is the feature you are proposing to solve the problem?
The proposed feature is to extend the current build process for community images on the RapidFort platform to include ARM64 variants. Given that ARM64 support is already available for non-community images, I see no technical barrier to providing the same for community containers.
What alternatives have you considered?
There are currently no viable alternatives to the existing offering, which is why I am submitting this issue for review.
The text was updated successfully, but these errors were encountered:
Name and Version
rapidfort/*
What is the problem this feature will solve?
Given that the RapidFort platform already supports ARM64 for non-community images, it would be highly advantageous to extend ARM64 compatibility to the community containers. With the growing adoption of ARM-based architectures—exemplified by M-series Macs and Snapdragon-powered Windows laptops—supporting an ARM64 variant for community images is becoming increasingly essential.
Furthermore, I see no evident technical barrier preventing the release of ARM64 containers. There should be no reason to continue releasing only x86/64 containers when the RapidFort platform already supports ARM64, as this would ensure broader device compatibility and inclusivity for emerging ARM-powered platforms.
What is the feature you are proposing to solve the problem?
The proposed feature is to extend the current build process for community images on the RapidFort platform to include ARM64 variants. Given that ARM64 support is already available for non-community images, I see no technical barrier to providing the same for community containers.
What alternatives have you considered?
There are currently no viable alternatives to the existing offering, which is why I am submitting this issue for review.
The text was updated successfully, but these errors were encountered: