Failed to mount blob storage to AKS using azureblob-nfs-premium

Erodotos D. Demetriou 20 Reputation points


I am trying to mount an Azure Blob Storage Account to my AKS with the following error:

Output: mount.nfs: mounting <storage-account-name><storage-account-name>/<blob-container-name> failed, reason given by server: No such file or directory

Note that the storage account is using private endpoints. To make sure that connectivity to the storage account is allowed, I used the following commands:

nc -v -w 2 <storage-account-name> 111 nc -v -w 2 <storage-account-name> 2048

Both commands succeeded and a connection was established.

What else shall I check to resolve my issue? Any guidance would be appreciated.

Thank you

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
1,961 questions
Azure Private Link
Azure Private Link
An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
384 questions
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,554 questions
{count} votes

Accepted answer
  1. Ramya Harinarthini_MSFT 4,126 Reputation points Microsoft Employee

    @Erodotos D. Demetriou

    NFS 3.0 error 1: Exit status 32. No such file or directory

    Cause: Blob container doesn't exist

    To check if the Blob container exists, follow these steps:

    Search for Storage accounts in the Azure portal and access your storage account.

    [Screenshot that shows how to search a storage account.


    Select Containers under Data storage in the storage account and check if the associated PersistentVolume (PV) exists in Containers. To see the Persistent Volume (PV), check the Persistent Volume Claim (PVC) associated with the pod in the YAML file, and then check which PV is associated with that PVC.

    [Screenshot that shows the Persistent Volume Claim (PVC).


    Solution: Ensure the Blob container exists

    To resolve this issue, make sure that the Blob container that's associated with the PV/PVC exists.

    Reference Article:

    Also, please share blob driver POD logs from which is running on the NODE from where this application POD is being scheduled.

    Please let us know if you have any further queries. I’m happy to assist you further.

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

0 additional answers

Sort by: Most helpful