running quake-kube on RPI4 about quake-kube HOT 5 CLOSED

Runs so well! Thank you for this, you guys are great.

from quake-kube.

A first pass at this might look like:

• try and compile ioquake on the RPi4 (or cross compile targeting ARMv8/arm64 - I only see special cases for v7 referenced in their makefile but v8 might just work)
• modify our Dockerfile to compile the Go binaries to ARM (GOARCH=arm64) and then either remove the multistage build step for ioquake and instead copy in your ARMv8 built binaries, or, better, modify the whole multistage build to work correctly on multiarch
• push the resultant Docker image to a registry and change the reference in our example deployment to your image.

Ideally, once it is working, we could then update our build to cross-compile and publish a multiarch Docker image - Kubernetes/Docker/etc will pull the correct specific image for the architecture that they're running on out of a multiarch image tag and the end-user experience would be just deploying the same example manifests 🎉

from quake-kube.

@mahalel those are all great suggestions from @rbtr. I was needing to take a look at docker buildx, a container cross-compiling toolkit, for a different project, so i ended up giving the last suggestion a go. I followed this blog post on setting it up:

https://community.arm.com/developer/tools-software/tools/b/tools-software-ides-blog/posts/getting-started-with-docker-for-arm-on-linux

I think with the changes to the Dockerfile that are in #12, you should be able to build the container on the rpi4 itself as well (although I haven't tested yet).

from quake-kube.

@mahalel I think the changes in #12 should allow this to run on the RPI4. I'm closing the issue, but please feel free to reopen (or open a new issue) if you run into more issues or have more questions. Thanks again for bringing this up!

from quake-kube.

Sorry for not getting back faster, appreciate all the replies so far - will give this a go and report back :)

from quake-kube.