![]() Image: gcr.io/google-containers/kube-apiserver:v1.16.3 $ docker container run mplatform/mquery gcr.io/google-containers/kube-apiserver:v1.16.3 For example, the Kubernetes project publishes Docker images that are built for multiple architectures: $ kubectl run -i -rm -image busybox whats-my-arch -restart Never - uname -mĪre there Docker images that support multiple architectures? This was never a problem whilst our local computer, our CI system, and our production system all used the same architecture: the famous “Intel Inside” x86 and clone-makers like AMD. Tiller-deploy-585d9c49b6-v646t 0/1 CreateContainerError 6 6h25mĭocker images will “run anywhere” only if the image was built for the same computer architecture. The joy of seeing my new cluster running was soon doused with a fun-retardant called CreateContainerError: Raspberrypi3-lightblue Ready master Raspbian GNU/Linux 10 (buster) Raspberrypi3-white Ready Raspbian GNU/Linux 10 (buster) ![]() Raspberrypi3-red NotReady Raspbian GNU/Linux 10 (buster) ![]() $ kubectl get nodes -o wideNAME STATUS ROLES OS-IMAGE ![]() In my first iteration, I have one Pi running Kubernetes master, and two Pis as workers only: I’ve started a new home lab of Raspberry Pis (and soon to include some old Intel laptops) running k3s distribution of Kubernetes. Why? What do we need to do? This article introduces the “docker buildx” plugin to make it easy to produce mult-arch Docker images. Nearly every Docker image you’ve ever run on Kubernetes will not work on your Homelab Raspberry Pi cluster.
0 Comments
Leave a Reply. |