Does anyone have any ideas about how the kernel's nfsd should interact (if at all) with network namespaces? I'm initially interested because I've been experimenting with modifying the server to allow it to present different exported filesystems depending on which ip address it's accessed through. One way to do that might be by modifying the kernel to behave as though there's a separate nfsd service per network namespace; then we'd need little or no modification of the userspace support daemons (statd, the portmapper, etc.)--just start multiple instances of them in separate network namespaces and teach the kernel to route requests to them to the corresponding loopback interface. (That would work at least for daemons that communicate with the kernel exclusively using rpc over loopback. We could perhaps do something similar with the various /proc and nfsctl interfaces.) I'm also curious more generally whether anyone's thought about how nfsd should behave in the presence of containers. (Also, I take it the sysfs problem described in http://lwn.net/Articles/295587/ is still unsolved?) --b. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
