Unable to create Pod .Please provide Solution for this error .

Question

I created sample Web Application and published it to ACR.When i tried creating deployment it errored with following Message

Error: failed to create containerd container: mount callback failed on /var/lib/containerd/tmpmounts/containerd-mount732009033: open /var/lib/containerd/tmpmounts/containerd-mount732009033/etc/passwd: no such file or directory

Deployment File

apiVersion: apps/v1
kind: Deployment
metadata:
name: razsite
labels:
app: web
spec:
replicas: 2
selector:
matchLabels:
app: web
template:
metadata:
labels:
app: web

spec:
 containers:
   - name: app
     image: aciraz.azurecr.io/myfirstdockerwebapp:latest
     ports:
        - containerPort: 80
     resources:
      requests:
       memory: "64Mi"
       cpu: "250m"
      limits:
         memory: "128Mi"
         cpu: "500m"

Answer 1

apiVersion: apps/v1
kind: Deployment
metadata:
name: razsite
labels:
app: web
spec:
replicas: 2
selector:
matchLabels:
app: web
template:
metadata:
labels:
app: web

spec:
 containers:
   - name: app
     image: aciraz.azurecr.io/myfirstdockerwebapp:latest
     ports:
        - containerPort: 80
     resources:
      requests:
       memory: "64Mi"
       cpu: "250m"
      limits:
         memory: "128Mi"
         cpu: "500m"

Answer 2

I actually got the same error. Created various different helm3 charts, different services, etc. Always the deployment is stuck with this error.

Answer 3

As we migrated to K8 Version 1.22.11 this problem started. Previously the containers worked fine. It was only after upgrading the cluster (not the images). The problem continues for versions 1.23.5, and 1.23.8. Since there is no way to gracefully downgrade the clusters; is there a reason for this. Rebuilding and not updating seems to be a bad option. @Gero Landmann @Razia Sulthana B

Answer 4

Seems if you build the image on win instead of linux, this issue will happen. see this https://github.com/Azure/AKS/issues/2369

Answer 5

@Lynn Niu We looked into that; but our pipeline continues to use Ubuntu:latest for the build. No change there.