Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing fails #7

Open
jantoine1 opened this issue May 1, 2018 · 0 comments
Open

Testing fails #7

jantoine1 opened this issue May 1, 2018 · 0 comments

Comments

@jantoine1
Copy link

Following the Testing section in the README.md file, the NFS share won't mount.

When running mount -t nfs -v -o nolock,vers=3 nfs:/exports /nfs, I get the following output:

mount.nfs: timeout set for Tue May  1 01:02:04 2018
mount.nfs: trying text-based options 'nolock,vers=3,addr=172.17.0.3'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 172.17.0.3 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 172.17.0.3 prog 100005 vers 3 prot TCP port 1892
mount.nfs: Protocol not supported

When running ls -al /nfs, I get the following output:

total 8
drwxr-xr-x  2 root root 4096 May  1 00:59 .
drwxr-xr-x 41 root root 4096 May  1 00:59 ..

Execing into the nfsserver container, I can see that the /exports directory has the date file created.

I've tried troubleshooting the nfsserver, but all online help that I could find doesn't seem to apply since the NFS server is a custom NodeJS app and not the linux kernel.

Any help resolving this would be greatly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant