kubernetes: mkdir read-only file system: unknown

[hazcod]

Checks

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: 8F32DCD2-92AD-48DB-8BCB-1E1433359FC4/20210106160313

Expected behavior

I should be able to deploy a kubernetes application with a read-only root filesystem and a volume mount.

Actual behavior

Installation via helm returns

Name:         backend-96c7d4646-pnjjl
Namespace:    venclave
Priority:     0
Node:         docker-desktop/192.168.65.3
Start Time:   Wed, 06 Jan 2021 17:00:01 +0100
Labels:       app=backend
              owner=hazcod
              pod-template-hash=96c7d4646
Annotations:  container.seccomp.security.alpha.kubernetes.io/backend: runtime/default
              seccomp.security.alpha.kubernetes.io/pod: runtime/default
Status:       Running
IP:           10.1.0.9
IPs:
  IP:           10.1.0.9
Controlled By:  ReplicaSet/backend-96c7d4646
Containers:
  backend:
    Container ID:   docker://b6229c8d7d3f453db36fa0a98bef83117af4bcfd9c99cfc7ef54d80547d7b99e
    Image:          ghcr.io/ironpeakservices/micro-backend/backend:dev
    Image ID:       docker://sha256:90028e3bdb75b7037cf69d0beceada4175566c4abefd8235d8c89b22a8fc11d0
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       ContainerCannotRun
      Message:      OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting "/var/lib/kubelet/pods/93cb4733-b1aa-4d23-87e8-31e1f6ba0c01/volumes/kubernetes.io~empty-dir/backend-cache" to rootfs at "/var/lib/docker/overlay2/91455f2181a83ed91f032184f533a9eb102b9111f492351c75cba9a9aa8abd37/merged/site/resources" caused: mkdir /var/lib/docker/overlay2/91455f2181a83ed91f032184f533a9eb102b9111f492351c75cba9a9aa8abd37/merged/site/resources: read-only file system: unknown
      Exit Code:    128
      Started:      Wed, 06 Jan 2021 17:01:33 +0100
      Finished:     Wed, 06 Jan 2021 17:01:33 +0100
    Ready:          False
    Restart Count:  4
    Limits:
      cpu:     500m
      memory:  300Mi
    Requests:
      cpu:        500m
      memory:     300Mi
    Environment:  <none>
    Mounts:
      /site from backend-localdev (ro)
      /site/resources from backend-cache (rw)
      /tmp/hugo_cache from backend-cache (rw)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  backend-localdev:
    Type:          HostPath (bare host directory volume)
    Path:          /Users/niels/Source/ironpeak/micro-backend
    HostPathType:  
  backend-cache:
    Type:        EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:      Memory
    SizeLimit:   <unset>
QoS Class:       Guaranteed
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  2m12s                default-scheduler  Successfully assigned venclave/backend-96c7d4646-pnjjl to docker-desktop
  Normal   Created    40s (x5 over 2m11s)  kubelet            Created container backend
  Normal   Pulled     40s (x5 over 2m11s)  kubelet            Container image "ghcr.io/ironpeakservices/micro-backend/backend:dev" already present on machine
  Warning  Failed     40s                  kubelet            Error: failed to start container "backend": Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting "/var/lib/kubelet/pods/93cb4733-b1aa-4d23-87e8-31e1f6ba0c01/volumes/kubernetes.io~empty-dir/backend-cache" to rootfs at "/var/lib/docker/overlay2/91455f2181a83ed91f032184f533a9eb102b9111f492351c75cba9a9aa8abd37/merged/site/resources" caused: mkdir /var/lib/docker/overlay2/91455f2181a83ed91f032184f533a9eb102b9111f492351c75cba9a9aa8abd37/merged/site/resources: read-only file system: unknown
  Warning  BackOff    5s (x9 over 2m5s)    kubelet            Back-off restarting failed container

Information

• macOS Version: 11.1
• Docker for Mac: 3.0.3

Steps to reproduce the behavior

See describe above.

[vishal31aug]

same error on different application on k8s , did you find the solution of the error

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked