Seems to me that the only sane way for production, is persistence-as-a-service.
Whether that means NFS, shared volumes with some kind of cluster fs -- or something else -- I don't think some hackish ux on top of folders located at a magic path on the docker host is a particularly robust or elegant solution.
That said, if you're going to use folders mapped on the host anyway, integrating them with docker (like volumes does) seems like a good idea.
Would much prefer some sane networked system (perhaps with some optimizations for loopback/local use), possibly blessing NFS/CIFS/p9fs for file-systems, and some kind of block storage ("s3"/drbd/iscsi) for, well, block storage.
Adding to that, are there any really working implementations for 9p client/server for Linux? It looks like it should be beautiful and smell of flowers, but the reality seems a lot more half-hearted...
Whether that means NFS, shared volumes with some kind of cluster fs -- or something else -- I don't think some hackish ux on top of folders located at a magic path on the docker host is a particularly robust or elegant solution.
That said, if you're going to use folders mapped on the host anyway, integrating them with docker (like volumes does) seems like a good idea.
Would much prefer some sane networked system (perhaps with some optimizations for loopback/local use), possibly blessing NFS/CIFS/p9fs for file-systems, and some kind of block storage ("s3"/drbd/iscsi) for, well, block storage.
Adding to that, are there any really working implementations for 9p client/server for Linux? It looks like it should be beautiful and smell of flowers, but the reality seems a lot more half-hearted...