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

Razia Sulthana B 6 Reputation points
2021-04-27T19:19:09.993+00:00

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"
Visual Studio Testing
Visual Studio Testing
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Testing: The act or process of applying a test as a means of analysis or diagnosis.
252 questions
No comments
1 vote

5 answers

Sort by: Most helpful
  1. Razia Sulthana B 6 Reputation points
    2021-04-27T19:23:44.85+00:00

    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"
    
    No comments

  2. Gero Landmann 1 Reputation point
    2021-06-27T21:04:52.543+00:00

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

    No comments

  3. O'Brien, Joe 1 Reputation point
    2022-08-11T23:13:24.457+00:00

    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

    No comments

  4. Lynn Niu 231 Reputation points
    2022-08-12T03:22:53.42+00:00

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

    No comments

  5. Joe O'Brien 1 Reputation point
    2022-08-12T14:09:19.413+00:00

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

    No comments