docker-nfs-server as a "data/system snapshot engine": feasible? about docker-nfs-server

[johnnyutahh]

Upon further reading of https://github.com/ehough/docker-nfs-server#starting-the-server :

Does "Provide the files to be shared over NFS ... from... files baked into custom image" mean that the docker-nfs-server container would read-and-write files directly from another docker container that contains/stores the files?

If so, by what means does it do this -- ie, how does the docker-nfs-server container communicate with files served by the filesystem in the "data container"?

(I'm unclear on what Docker's copy command does in this context; specifically, what does "baked into" mean? Which files get copied where, etc?)

[johnnyutahh]

At some point I'll be "cracking the hood and rebuilding the engine" (hopefully it's a minor rebuild, if no rebuild at all) to support my use case, which is totally cool and what I initially expected to do anyway.

I am trying to get @ehough 's attention by other means with as of yet no success. I've been preparing to do this work at some near-term, future point in hopes that Eric comes in and says "oh yeah, this is easy, just do 'X'" and saves my team some effort, while we work on other-more-pressing tasks.

In any case, the output from Eric's efforts looks (without yet testing it) remarkably good, and my team and I are very appreciative to not have to build a more-robust nfs-server container from scratch. Thanks Eric!