# Nfs-client-provisioner not working from inside cluster

**URL:** <https://forums.suse.com/t/nfs-client-provisioner-not-working-from-inside-cluster/14475>\
**Category:** SUSE Rancher Prime\
**Created:** [June 6, 2019, 3:47pm UTC](https://forums.suse.com/t/nfs-client-provisioner-not-working-from-inside-cluster/14475 "2019-06-06T15:47:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Flavio\_Campana](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/flavio_campana/32/3994_2.png) [@Flavio\_Campana](https://forums.suse.com/u/Flavio_Campana)\
**Post date:** [June 6, 2019, 3:47pm UTC](https://forums.suse.com/t/nfs-client-provisioner-not-working-from-inside-cluster/14475/1 "2019-06-06T15:47:15Z")

</div>

Hi,  
i’m trying to use nfs-client-provisioner but i’m encountering some troubles.  
I got 3 server with proxmox and a freenas one, and a common centos vm on a proxmox node can easily mount nfs shares from freenas.  
I made a small cluster with rancheros as base os and everything else seems to work well.  
When i try to install nfs-client-provisioner with helm, i always get a timeout on the pods.  
I then tried gettin inside a bash cli from an ubuntu container, and i got this message : Output: mount.nfs: rpc.statd is not running but is required for remote locking.  
mount.nfs: Either use ‘-o nolock’ to keep locks local, or start statd.

What am i doing wrong?  
Thanks
