NFS problem in LXC container

Hi everybody. I have been trying to get NFS to work with my router all day. Sadly things seem to be buggy.

I have configured a standard debian LXC container on Turris, running on 192.168.1.203.
With a standard exportsfile.

root@nestor:~# cat /etc/exports

/etc/exports: the access control list for filesystems which may be exported

to NFS clients. See exports(5).

Example for NFSv2 and NFSv3:

/srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)

Example for NFSv4:

/srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)

/srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)

/home 192.168.1.196(rw,sync,subtree_check)

But when I try to mount it I get errorrs

root@comp:~# mount -o tcp,vers=3 -vv 192.168.1.203:/home /tmp/test
mount.nfs: timeout set for Sat Mar 11 19:41:57 2017
mount.nfs: trying text-based options 'tcp,vers=3,addr=192.168.1.203’
mount.nfs: prog 100003, trying vers=3, prot=6

I have also tried getting NFS to work on turris, and to my suprice, there is a live and active exports file

root@turris:~# cat /etc/exports
/mnt *(ro,all_squash,insecure,sync)

But you cant mount it, even on localhost

/etc/exports is the configuration file, but you don’t provide any information about whether the server is running that configuration file.

What’s the out put of running exportfs?

# exportfs
exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 2 (No such file or directory)

Also what’s the output for ps after I started nfs:

# ps | grep nfs
1272 root 0 SW< [nfsiod]
23589 root 1188 S {nfsd} /bin/sh /etc/rc.common /etc/init.d/nfsd start
23599 root 840 D /usr/sbin/rpc.nfsd
23676 root 1092 S grep nfs

(as a side note, you should probably escape any # symbols (\#) otherwise it bolds your text in the forum)

root@nestor:/ exportfs
/home 192.168.1.0/255.255.255.0

root@nestor:/ ps | grep nfs
root@nestor:/

I am running the kernel-nfs version. Not sure why of if its a good ide on an LXC container.

Please note that if I would comment out the entry in exports I will get a different error on the client side.