Build artifacts and images for linux/riscv64 #4444
Conversation
Signed-off-by: Matheus Macabu <macabu.matheus@gmail.com>
To be honest I don't know if the Go team has such a thing as different support "tiers". RISC-V target is recent (from Go 1.21.0), but in my experience building a bunch of different projects, I haven't had any weird compiler error, crash, or misbehaving as far as my tests went. |
|
It's not so much about "support tiers" as it is about Go runtime support. It seems though that it's more or less "covered" https://groups.google.com/g/golang-nuts/c/m4OF6nieGro |
There was a problem hiding this comment.
I think this is fine so LGTM, but let's see what other maintainers say :)
PTAL @thaJeztah
Thanks for linking it, I wasn't aware 🙇 |
|
FWIW; if the intent is to also have riscv variants in the official image, then changes are probably also needed in https://github.com/distribution/distribution-library-image and https://github.com/docker-library/official-images/blob/fb18daaa4388ddc39121d22701d9c0e266c61e27/library/registry |
|
Of course. It'll be done. At some point. |
|
Let me know and I can test it! Would this make the cut for 3.0 or later? |
The only notable change is the addition of riscv plaform. See: distribution/distribution#4444 Signed-off-by: Milos Gajdos <milosthegajdos@gmail.com>
As part of the effort to be able to build
moby/mobyin Docker-in-Docker fashion forlinux/riscv64natively, it requires this image to be build so as well.Dependency from https://github.com/moby/moby/blob/master/Dockerfile#L95
I've been able to build and do a basic run of the binary in my riscv64 host: