<p>While deploying a new deployment to our GKE cluster, the pod is created but is failing with the following error:</p>

<pre><code>Failed create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:319: getting the final child's pid from pipe caused \"read init-p: connection reset by peer\"": unknown
</code></pre>

<p>The cluster is not loaded at all, and there is enough free disk, memory and CPU.</p>

<p>No other issue was seen in the pod/cluster logs.</p>

hilsenrat
<p>The issue was eventually in the deployment YAML.</p>

<p>If you encounter a similar issue, check your resources section and verify it has to correct syntax which can be found here: <a href="https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/" rel="noreferrer">https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/</a> </p>

<p>In my case, the issue was in the memory value:</p>

<p><strong>Working example (Note the Mi):</strong></p>

<pre><code>resources:
    limits:
      cpu: 500m
      memory: 256Mi
    requests:
      cpu: 5m
      memory: 256Mi
</code></pre>

<p><strong>The initial resources definition (BAD SYNTAX):</strong></p>

<pre><code>resources:
    limits:
      cpu: 500m
      memory: 256m
    requests:
      cpu: 5m
      memory: 256m
</code></pre>

<p>I hope that it'll help other community members in the future, since it took me a decent amount of time to find the root cause in my case...</p>
