-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] RISC-V support #22824
[RFC] RISC-V support #22824
Conversation
Does it also work with Alpine 3.18? We currently cannot migrate to 3.20 since this makes the Docker build hang. |
It does not, Alpine 3.20 is the first version that supports the RISC-V architecture. |
Then I will hold this until the bug in Node 20 is fixed (Alpine 3.18 is the last to use Node 18 which doesnt have this bug) |
Understood! Out of curiosity, is there any issue for that bug in Node 20? Also, interestingly enough, CI for this PR succeeded, while it previously hung in my fork and was terminated after 360 minutes. |
Ci succeeds because it doesnt build the container (which is what fails for armv7 and 6 platforms on node 20) |
This is in prepartion of publishing container images for the RISC-V architecture.
…ome Assistant event entities are enabled Koenkk#25133
|
riscv is not officially supported by |
@Koenkk had to add |
This PR updates the Alpine base container to Alpine 3.20, which supports the RISC-V architecture, and enables 64-bit RISC-V builds in Github actions.
I understand this probably won't be merged soon, due to the Alpine bump and the potential for regressions, but like this people who have RISC-V hardware lying around, can give it a try. I'm personally running a locally built zigbee2mqtt container on the VisionFive 2 for the past week and it's been working rather well.