EFSMountError cloud runtime_error ai_generated true

Failed to mount EFS filesystem: resource temporarily unavailable

ID: cloud/gcp-cloud-run-efs-mount-missing

Also available as: JSON · Markdown · 中文
78%Fix Rate
85%Confidence
1Evidence
2024-03-15First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
Cloud Run (managed) gcloud 450.0.0 active — — —
AWS EFS (via VPC connector) active — — —

Root Cause

Cloud Run service cannot mount an EFS file system because the VPC connector is misconfigured or the EFS mount target is in a different subnet without proper routing.

generic

中文

Cloud Run服务无法挂载EFS文件系统，因为VPC连接器配置错误或EFS挂载目标位于不同子网且缺少正确路由。

Official Documentation

https://cloud.google.com/run/docs/configuring/vpc-connectors

Workarounds

  1. 75% success Verify the VPC connector is in the same VPC and subnet as the EFS mount target. Use `gcloud compute networks vpc-access connectors describe CONNECTOR_NAME` to check network configuration. Then ensure the EFS security group allows inbound NFS (port 2049) from the VPC connector's CIDR. 
    Verify the VPC connector is in the same VPC and subnet as the EFS mount target. Use `gcloud compute networks vpc-access connectors describe CONNECTOR_NAME` to check network configuration. Then ensure the EFS security group allows inbound NFS (port 2049) from the VPC connector's CIDR.
  2. 85% success Add a VPC connector with a static IP range that overlaps the EFS mount target subnet. Example: `gcloud compute networks vpc-access connectors create my-connector --region us-central1 --network default --range 10.8.0.0/28` 
    Add a VPC connector with a static IP range that overlaps the EFS mount target subnet. Example: `gcloud compute networks vpc-access connectors create my-connector --region us-central1 --network default --range 10.8.0.0/28`

中文步骤

  1. Verify the VPC connector is in the same VPC and subnet as the EFS mount target. Use `gcloud compute networks vpc-access connectors describe CONNECTOR_NAME` to check network configuration. Then ensure the EFS security group allows inbound NFS (port 2049) from the VPC connector's CIDR.
  2. Add a VPC connector with a static IP range that overlaps the EFS mount target subnet. Example: `gcloud compute networks vpc-access connectors create my-connector --region us-central1 --network default --range 10.8.0.0/28`

Dead Ends

Common approaches that don't work:

  1. Increase Cloud Run memory limit 60% fail

    Memory limit does not affect NFS mount availability; the error is network-related.

  2. Recreate the EFS file system 80% fail

    The file system itself is healthy; the issue is in the network path between Cloud Run and EFS.