<p>I run the following commands and when I check if the pods are running I get the following errors:</p>

<blockquote>
  <p>Failed to pull image "tomcat": rpc error: code = Unknown desc = no
  matching manifest for linux/amd64 in the manifest list entries</p>
</blockquote>

<pre><code>kubectl run tomcat --image=tomcat --port 8080
</code></pre>

<p>and</p>

<blockquote>
  <p>Failed to pull image "ngnix": rpc error: code = Unknown desc
  = Error response from daemon: pull access denied for ngnix, repository does not exist or may require 'docker login'</p>
</blockquote>

<pre><code>kubectl run nginx3 --image ngnix --port 80
</code></pre>

<p>I seen a post in git about how to complete this when private repos cause an issue but not public. Has anyone ran into this before?</p>

<p><strong>First Problem</strong></p>

<p>From github <a href="https://github.com/docker-library/official-images/issues/3835" rel="noreferrer">issue</a></p>

<blockquote>
  <p>Sometimes, we'll have non-amd64 image build jobs finish before their amd64 counterparts, and due to the way we push the manifest list objects to the library namespace on the Docker Hub, that results in amd64-using folks (our primary target users) getting errors of the form "no supported platform found in manifest list" or "no matching manifest for XXX in the manifest list entries"</p>
</blockquote>

<p>Docker Hub manifest list is not up-to-date with <code>amd64</code> build for <code>tomcat:latest</code>.</p>

<p>Try another tag</p>

<pre><code>kubectl run tomcat --image=tomcat:9.0 --port 8080
</code></pre>

<p><strong>Second Problem</strong></p>

<p>Use <code>nginx</code> not <code>ngnix</code>. <em>Its a typo</em>.</p>

<pre><code>$ kubectl run nginx3 --image nginx --port 80
</code></pre>
