<p>I am trying to debug my pod throwing CrashLoopBackOff error. When I run decribe command, I found that <code>Back-off restarting failed container</code> is the error. I excuted the logs for the failing pod and I got the below data.</p>
<pre><code>vagrant@master:~&gt; kubectl logs pod_name
standard_init_linux.go:228: exec user process caused: exec format error

vagrant@master:/vagrant&gt; kubectl logs -p  pod_name
unable to retrieve container logs for containerd://db0f2dbd549676d8bf1026e5757ff45847c62152049b36037263f81915e948eavagrant
</code></pre>
<p>Why I am not able to execute the logs command?</p>
<p>More details:</p>
<p><a href="https://i.stack.imgur.com/wIejs.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/wIejs.png" alt="enter image description here" /></a></p>
<p>yaml file is as follows</p>
<pre><code>apiVersion: v1
kind: Service
metadata:
  labels:
    service: udaconnect-app
  name: udaconnect-app
spec:
  ports:
  - name: &quot;3000&quot;
    port: 3000
    targetPort: 3000
    nodePort: 30000
  selector:
    service: udaconnect-app
  type: NodePort
---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    service: udaconnect-app
  name: udaconnect-app
spec:
  replicas: 1
  selector:
    matchLabels:
      service: udaconnect-app
  template:
    metadata:
      labels:
        service: udaconnect-app
    spec:
      containers:
      - image: udacity/nd064-udaconnect-app:latest
        name: udaconnect-app
        imagePullPolicy: Always
        resources:
          requests:
            memory: &quot;128Mi&quot;
            cpu: &quot;64m&quot;
          limits:
            memory: &quot;256Mi&quot;
            cpu: &quot;256m&quot;
      restartPolicy: Always
</code></pre>
<p>My vagrant file</p>
<pre><code>default_box = &quot;opensuse/Leap-15.2.x86_64&quot; 
Vagrant.configure(&quot;2&quot;) do |config|
config.vm.define &quot;master&quot; do |master|
    master.vm.box = default_box
    master.vm.hostname = &quot;master&quot;
    master.vm.network 'private_network', ip: &quot;192.168.0.200&quot;,  virtualbox__intnet: true
    master.vm.network &quot;forwarded_port&quot;, guest: 22, host: 2222, id: &quot;ssh&quot;, disabled: true
    master.vm.network &quot;forwarded_port&quot;, guest: 22, host: 2000 # Master Node SSH
    master.vm.network &quot;forwarded_port&quot;, guest: 6443, host: 6443 # API Access
    for p in 30000..30100 # expose NodePort IP's
      master.vm.network &quot;forwarded_port&quot;, guest: p, host: p, protocol: &quot;tcp&quot;
      end
    master.vm.provider &quot;virtualbox&quot; do |v|
      v.memory = &quot;3072&quot;
      v.name = &quot;master&quot;
      end
    master.vm.provision &quot;shell&quot;, inline: &lt;&lt;-SHELL
      sudo zypper refresh
      sudo zypper --non-interactive install bzip2
      sudo zypper --non-interactive install etcd
      sudo zypper --non-interactive install apparmor-parser
      curl -sfL https://get.k3s.io | sh -
    SHELL
  end

  config.vm.provider &quot;virtualbox&quot; do |vb|
  vb.memory = &quot;4096&quot;
      vb.cpus = 4
end
</code></pre>
<p>Any help is appreciated.</p>

<p>Summarizing the comments: <code>CrashLoopBackOff</code> error occurs, when there is a mismatch of AMD64 and ARM64 devices. According to your docker image <code>udacity/nd064-udaconnect-app</code>, we can see that it's <a href="https://hub.docker.com/r/udacity/nd064-udaconnect-app/tags" rel="nofollow noreferrer">AMD64 arch</a> and your box <code>opensuse/Leap-15.2.x86_64</code> is <a href="https://en.opensuse.org/openSUSE:AArch64" rel="nofollow noreferrer">ARM64 arch</a>.</p>
<p>Hence, you have to change either your docker image, or the box in order to resolve this issue.</p>
