-
Notifications
You must be signed in to change notification settings - Fork 22
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
No ARM support #7
Comments
I'll need to take a look how to coax GitHub Actions to build for RPi's, the docker build file should support it out of the box. |
Hmm.. I meant to ask you to confirm if the image works before I tag a new release to update the |
Thanks, but unfortunately I don't have an arm64 device to test with. TBH they're a bit unusual still (but growing). Raspberry Pi OS is primarily distributed in 32 bits. It's only recently that 64 bit OSes have become available for the pi4, specifically. You need to add |
Oh, I didn't realize that they still default to 32 bit, let me adjust the build rules to see if I can trick it to build a 32 bit version too. |
FWIW I manually tested the arm64 image with qemu and it works. Here's my qemu command.
|
Thanks for checking. I should have all the relevant build rules in place to build armv7 images along with everything else, but it seems that GitHub is having issues with the build token permissions so I'll retry builds during next week. |
There we go, permission issues resolved and build is running for |
Just confirmed that multi-arch build succeeded and https://github.com/ressu/kube-plex/pkgs/container/kube-plex/7948865 has arm/v7 support too. So when ever I tag the next release, arm/v7 will automatically build for the releases. The normal CI builds are only built for amd64, since the other builds take much longer to complete. |
Looks like the image at
quay.io/munnerz/kube-plex
doesn't have arm support. It would be easy to cross-build and put up our own image on ghcr, and enable compatibility for raspberry pi's, pinebooks, and other arm devices.The text was updated successfully, but these errors were encountered: