-
Notifications
You must be signed in to change notification settings - Fork 221
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
How to provide for Docker Volume ? #87
Comments
Try mount $ sudo mount -v -t nfs -o rw,vers=3,nolock,proto=udp,port=2049 196.168.100.134:/nfs/nas ./nas_dir
mount.nfs: timeout set for Thu Jul 18 16:01:37 2024
mount.nfs: trying text-based options 'vers=3,nolock,proto=udp,port=2049,addr=196.168.100.134'
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out $ sudo mount -v -t nfs -o rw,vers=4,nolock,proto=udp,port=2049 196.168.100.134:/nfs/nas ./nas_dir
mount.nfs: timeout set for Thu Jul 18 16:04:39 2024
mount.nfs: trying text-based options 'nolock,proto=udp,port=2049,vers=4.2,addr=196.168.100.134,clientaddr=192.168.100.131'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'nolock,proto=udp,port=2049,vers=4,minorversion=1,addr=196.168.100.134,clientaddr=192.168.100.131'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'nolock,proto=udp,port=2049,vers=4,addr=196.168.100.134,clientaddr=192.168.100.131'
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified for /home/seepine/nas_dir |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm sorry, I can't find where the problem is, and I can only seek help here.
Nfs Server with docker-compose
In ubuntu24 server
192.168.100.134
And the log
For docker volume
But i got error msg
The text was updated successfully, but these errors were encountered: