error reading directory /var/run/efs: open /var/run/efs: no such file or directory I0812

[raja-gavva]

/kind bug

What happened?
we are upgrading EFS CSI controller from 2.1.4 to 2.1.10
we saw below error.
W0812 10:18:11.529911 1 efs_watch_dog.go:207] Error removing libwrap option from state files: error reading directory /var/run/efs: open /var/run/efs: no such file or directory

What you expected to happen?
we don't expected the above error of libwrap option with latest EFS CSI provisioning

How to reproduce it (as minimally and precisely as possible)?

Anything else we need to know?:

Environment

• Kubernetes version (use kubectl version): Client Version: v1.32.0
  Kustomize Version: v5.5.0
  Server Version: v1.31.10-eks-931bdca
• Driver version: 1.2.10

Please also attach debug logs to help us better diagnose
PS C:\Users\gavvasr\saml\aws-saml-connection\python3.6> kubectl get po -n efs-csi-controller
NAME READY STATUS RESTARTS AGE
efs-csi-controller-558969d54b-h2dgr 3/3 Running 0 30s
efs-csi-controller-558969d54b-wxcth 3/3 Running 0 30s
efs-csi-node-98r6c 3/3 Running 0 30s
efs-csi-node-xqpjg 3/3 Running 0 30s
efs-csi-node-zmmvd 3/3 Running 0 30s
PS C:\Users\gavvasr\saml\aws-saml-connection\python3.6> helm ls -n efs-csi-controller
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
aws-efs-csi-driver efs-csi-controller 1 2025-08-12 10:18:06.2203974 +0000 UTC deployed aws-efs-csi-driver-3.2.1 2.1.10
PS C:\Users\gavvasr\saml\aws-saml-connection\python3.6> kubectl logs efs-csi-controller-558969d54b-h2dgr -n efs-csi-controller
Defaulted container "efs-plugin" out of: efs-plugin, csi-provisioner, liveness-probe
I0812 10:18:11.519706 1 config_dir.go:63] Mounted directories do not exist, creating directory at '/etc/amazon/efs'
I0812 10:18:11.521729 1 metadata.go:67] getting MetadataService...
I0812 10:18:11.524192 1 metadata.go:72] retrieving metadata from EC2 metadata service
I0812 10:18:11.528955 1 driver.go:154] Did not find any input tags.
I0812 10:18:11.529334 1 driver.go:121] Registering Node Server
I0812 10:18:11.529345 1 driver.go:123] Registering Controller Server
I0812 10:18:11.529355 1 driver.go:126] Starting efs-utils watchdog
I0812 10:18:11.529435 1 efs_watch_dog.go:252] Copying /etc/amazon/efs/efs-utils.conf since it doesn't exist
I0812 10:18:11.529585 1 efs_watch_dog.go:252] Copying /etc/amazon/efs/efs-utils.crt since it doesn't exist
W0812 10:18:11.529911 1 efs_watch_dog.go:207] Error removing libwrap option from state files: error reading directory /var/run/efs: open /var/run/efs: no such file or directory
I0812 10:18:11.530101 1 driver.go:132] Starting reaper
I0812 10:18:11.530118 1 driver.go:141] Listening for connections on address: &net.UnixAddr{Name:"/var/lib/csi/sockets/pluginproxy/csi.sock", Net:"unix"}

• Instructions to gather debug logs can be found here

[raja-gavva]

we added below lines to values.tftpl and issue seems to be fixed.
volumes:
- name: efs-state-dir
emptyDir: {}
volumeMounts:
- name: efs-state-dir
mountPath: /var/run/efs

[TharaknadhBejavadaTR]

I am also facing the same issue where do we need to add above lines exactly ?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[raja-gavva]

I am also facing the same issue where do we need to add above lines exactly ?

under values.tftpl