The other option is to use hdfs or s3 or ceph or gluster, basically what I mean to say is to introduce a layer of indirection and have a dfs service with a userland "file system driver". I have used s3fs in my "experiments" with success although i would like to hear from others who have some real production use cases.
Sent from my iPhone > On Nov 22, 2014, at 5:53 PM, Kashif Ali <kas...@unixcraft.com> wrote: > > I've also thought about this, however I'm curious as to why others have not > used NFS in this way for solving storage issue with containers? > > The only thing I can think of is how do you make NFS HA and make it scale as > performance becomes an issue. You don't want to use a netapp etc.. Since > that won't work on public cloud etc.... Ideally you want an NFS cluster which > you can scale out to increase IO and disk capacity and also provide > resiliency. However the fact that know one has mentioned this on any blog > etc... I'm assuming there is a flaw somewhere or I am missing something > obvious. > > Regards, > > Kashif > >> On 22 Nov 2014, at 23:23, Timothy Chen <t...@mesosphere.io> wrote: >> >> Hi Qiang, >> >> It depends on how your NFS is setup, but if you have it mounted at the same >> location on each slave you simply just map that volume into your docker >> container with Mesos. >> >> Tim >> >> Sent from my iPhone >> >>> On Nov 22, 2014, at 9:40 AM, Qiang <qjavaswing2...@gmail.com> wrote: >>> >>> I having been working with docker and mesos recently and one of the app I >>> am going to dockerize relies on file storage, I thought about using NFS, >>> and docker data volume container, but I don't know how can I possibly use >>> these to address my problem, as far as I know, mesos has service discovery >>> but in my case I don't think a file storage can be made a service somehow. >>> >>> Any idea to save my day? >>> >>> Thanks, >>> >>> -- >>> Qiang Han
