|Number of watchers on Github||66|
|Number of open issues||1|
|Average time to close an issue||22 days|
|Average time to merge a PR||1 day|
|Open pull requests||1+|
|Closed pull requests||0+|
|Last commit||almost 2 years ago|
|Repo Created||almost 3 years ago|
|Repo Last Updated||8 months ago|
|Organization / Author||erezhorev|
|Do you use dockerized_nfs_server? Leave a review!|
|View dockerized_nfs_server activity|
|View on github|
|Latest Open Source Launches|
Trendy new open source projects in your inbox! View examples
privilegedflag in order to allow mount NFS filesystem, export it as docker volume (also for use by other containers) and overcome security modules limitations (e.g. 'selinux', 'appArmor'..etc).
docker run -d --name mynfs --cap-add=SYS_ADMIN erezhorev/dockerized_nfs_server
docker run -d --name mynfs --cap-add=SYS_ADMIN --security-opt apparmor:unconfined erezhorev/dockerized_nfs_server.
Activate the server by running the script start.sh.
For your convenience, it can also be sourced (e.g.
source start.sh) which will set the environment variable
MYNFSIP with the server's ip.
Behind stage it will automatically pull the docker image from Docker hub and start the nfs server container named 'mynfs' with the default export point:
(Docker internal run command:
docker run -d --name mynfs --privileged erezhorev/dockerized_nfs_server)
Optional arguments are allowed and transformed to export points with the default export (
/exports) as their root base path.
Legal arguments form:
start.sh share1 /share2 /some/share3 some/more/share4.
Arguments are allowed to include preceding Slash-'/' but its just the same as without it, each given argument transforms to an active export point under
share1 /share2 ->
Run: stop.sh (or
docker stop mynfs ; docker rm mynfs).
Note it also removes the server container with all its data!
To stop and preserve data, just run
docker stop mynfs instead.
status.sh as it includes the following info:
export points, server's stdout and running processes.
mount -v -t nfs -o proto=tcp,port=2049 [nfs server ip]:/exports/share1 /mnt/target_dir
docker exec -ti mynfs bash
And then, for example, you may run
netstat -tl to see if nfs is there.
lsmod | grep nfsd to see if the kernel module is there.
The nfs service of the docker container relies on the kernel of the native host to provide the kernel-level nfs support. If your nfs service is not up correctly, please make sure your native kernel does support nfs service.