<p>I have an Apple Macbook Pro with an M1 chip, where I have a local kubernetes cluster running through <code>Kind</code>. The thing is I don't understand how <code>Kind</code> deals with docker images from different platforms/architectures. The thing is I have an application installed via <code>Helm</code> that points to some docker images with <code>linux/amd64</code> architecture, and when I install it through <code>helm</code> (<code>helm install -n [namespace] [repo] [app]</code>), it works like a charm (I can actually look at the downloaded images and see that their architecture is <code>amd64</code>). However, when I download the same image to my local docker registry with <code>docker pull [my-image]</code>, and then try to load it to the <code>kind</code> cluster with <code>kind load docker-image [my-image] [my-cluster]</code>, it doesn't work and I get the following error:</p>
<pre><code>Image: &quot;[my-image]&quot; with ID &quot;sha256:d3a8...&quot; not yet present on node &quot;[my-cluster]-control-plane&quot;, loading...
ERROR: failed to load image: command &quot;docker exec --privileged -i [my-cluster]-control-plane ctr --namespace=k8s.io images import --digests --snapshotter=overlayfs -&quot; failed with error: exit status 1
Command Output: ctr: image might be filtered out
</code></pre>
<p>And after googling the error a little bit, I could see that it is due to the mismatch of architectures between the image and the <code>kind</code> cluster.</p>
<p>Could someone explain to me the reason for these different behaviors?</p>

<p>After asking in the <a href="https://kubernetes.slack.com/archives/CEKK1KTN2" rel="nofollow noreferrer">Kind Slack channel in the Kubernetes workspace</a> I could finally find the answer to my question: <a href="https://kubernetes.slack.com/archives/CEKK1KTN2/p1665033551816149" rel="nofollow noreferrer">whole thread here</a>.</p>
<p>TL,DR; <code>Kind</code> was unable to load the images with architectures that don't match the host architecture because it lacked a required <code>--all-platforms</code> argument in the call to the <code>ctr</code> tool used by <code>kind load docker-image</code> to load the docker images into the cluster. A <a href="https://github.com/kubernetes-sigs/kind/pull/2957" rel="nofollow noreferrer">PR to fix the issue</a> was filed and it will be fixed in future releases of <code>Kind</code>.</p>
