I am trying to switch to convoy-nfs but have run into an issue while starting. Our application really needs locking so I am wondering if locking was intentionally removed ?
What is the proper course of action to allow locking?
5/11/2016 9:46:04 PMWaiting for metadata 5/11/2016 9:46:04 PMtime="2016-05-12T04:46:04Z" level=info msg="Execing [/usr/bin/nsenter --mount=/proc/21656/ns/mnt -F -- /var/lib/docker/aufs/mnt/9362b696c64335f026344abfdbf1ba74329ff7e039ceb8828de7041c31f6aa8f/var/lib/rancher/convoy-agent/share-mnt --stage2 /var/lib/rancher/convoy/convoy-nfs-47f99cab-b92d-45c2-88cb-e086cad2775a -- /launch volume-agent-nfs-internal 21656]" 5/11/2016 9:46:04 PMRegistering convoy socket at /var/run/convoy-convoy-nfs.sock 5/11/2016 9:46:04 PMMounting at: /var/lib/rancher/convoy/convoy-nfs-47f99cab-b92d-45c2-88cb-e086cad2775a/mnt 5/11/2016 9:46:04 PMMounting nfs. Command: mount -t nfs -o rsize=32768,wsize=32768,noatime,intr XX.XX.XX.XX:/export/rdata/nsfdata /var/lib/rancher/convoy/convoy-nfs-47f99cab-b92d-45c2-88cb-e086cad2775a/mnt 5/11/2016 9:46:04 PMmount.nfs: rpc.statd is not running but is required for remote locking. 5/11/2016 9:46:04 PMmount.nfs: Either use '-o nolock' to keep locks local, or start statd. 5/11/2016 9:46:04 PMmount.nfs: an incorrect mount option was specified