Add installation documentation for ARM64

[chendave]

The guide here: https://minikube.sigs.k8s.io/docs/start/linux/ seems for X86 only, the deb package I get is not supported on ARM64,

# dpkg -i minikube_1.6.2.deb
dpkg: error processing archive minikube_1.6.2.deb (--install):
 package architecture (amd64) does not match system (arm64)
Errors were encountered while processing:
 minikube_1.6.2.deb

Is there any guide for installation for ARM64 and the deb is ready?

Thanks a lot!

[afbjorklund]

There is no guide just yet, since the support is still rather experimental (#5667) - still lacking a couple of images, for instance. So the support for building the deb was added, but we haven't started using it just yet. However, I think the binary is posted to GCS (even if not added to GitHub): minikube-linux-arm64

Usage should be very similar to normal, but some container images only have support for amd64. Originally Docker didn't have support for multiple architectures, but it has been added to newer images. You will need a powerful CPU like the Raspberry Pi 4 to run with kvm2, otherwise use none.

The main problem is the 2G memory requirement, which might mean having to add a swapfile...
There was also heat issues (overhearing) on the earlier modules, due to processing requirements.

But with the addition of more powerful ARM processors, it should work fine to run regular kubernetes.
So it will be regular deployment in a future version of minikube, with a minikube_1.6.2-0_arm64.deb

[afbjorklund]

Added a reminder to add the architecture to the package filenames in #6281

The main "problem" at the moment is that we only support the server use case... The main desktop OS solution (Raspbian) is using arm rather than arm64, and even though KVM is supported we don't have an ISO for that architecture. Same with the new docker driver (KIC), no ARM images for that. The kubeadm requirements (2 CPU, 4G RAM) also puts it at the high end of the available hardware.

So for the end user, the problems are similar to when running on a virtual desktop. And the total lack of isolation in the none driver still makes it non-recommended to use on a regular machine, and the use of sudo even makes it impractical for the client (since all the files end up being owned by root). The biggest long-term benefit of this form factor (RPi) also comes when running multiple such nodes locally.

But for trying it out, things "should work" now - on both the RPi3b and RPi4b.

• Add support for running on arm64 (aarch64) #5667 (comment)
• Request: add arm64 machine to CI (jenkins) #6280 (comment)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[sharifelgamal]

We support ARM64 now, but still do not have documentation for it. I'll keep this open for now.

[tstromberg]

It isn't pretty, but it looks like this was fixed: https://minikube.sigs.k8s.io/docs/start/

[afbjorklund]

It isn't pretty, but it looks like this was fixed: https://minikube.sigs.k8s.io/docs/start/

Added an issue to make it pretty: #10353