You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello there. I was able to set this container up with ease and confidence, so thank you for that.
I've run into a bit of a knowledge gap though - I'm not sure how to a) ensure devices external to the host (but still on the host's LAN) will be able to access the share, and b) have that functionality working on Windows (10 Pro). At present, my docker-compose.yaml looks like this:
If I don't forward :111, I am able to mount it referring to the container's IP from the host, as your readme suggests. And whether or not I permit NFS3, Windows just refuses to cooperate externally. I haven't tried an external Linux client yet, but I have a feeling that'll work just fine.
I originally tried without adding it to the reverse_proxy network, but it went ahead and created its own default network rather than using host or bridge. Obviously I'm least certain of what's right with this parameter specifically. =)
For completeness' sake, here's the command I'm using on Windows (with the NFS feature enabled, of course). mount -o anon \\10.0.0.1\nfs Z:
or mount -o anon \\192.168.4.10\nfs Z:
I can SSH from the Windows machine to the server via both of those NICs, so the fundamentals are in order. Or, the fundamentals I understand, anyway. =)
Any pointers would be much appreciated!
The text was updated successfully, but these errors were encountered:
Hello there. I was able to set this container up with ease and confidence, so thank you for that.
I've run into a bit of a knowledge gap though - I'm not sure how to a) ensure devices external to the host (but still on the host's LAN) will be able to access the share, and b) have that functionality working on Windows (10 Pro). At present, my
docker-compose.yaml
looks like this:If I don't forward :111, I am able to mount it referring to the container's IP from the host, as your readme suggests. And whether or not I permit NFS3, Windows just refuses to cooperate externally. I haven't tried an external Linux client yet, but I have a feeling that'll work just fine.
I originally tried without adding it to the reverse_proxy network, but it went ahead and created its own default network rather than using host or bridge. Obviously I'm least certain of what's right with this parameter specifically. =)
For completeness' sake, here's the command I'm using on Windows (with the NFS feature enabled, of course).
mount -o anon \\10.0.0.1\nfs Z:
or
mount -o anon \\192.168.4.10\nfs Z:
I can SSH from the Windows machine to the server via both of those NICs, so the fundamentals are in order. Or, the fundamentals I understand, anyway. =)
Any pointers would be much appreciated!
The text was updated successfully, but these errors were encountered: