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 re
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
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 wrote:
>
> I having been working with docker and m
You could use HDFS of Mount NFs on all nodes and then mount that inside all the
containers as a volume.
Sent from my iPhone
> On Nov 22, 2014, at 9:40 AM, Qiang 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 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
I have and it doesn't seem to add up. That being said, the growth of the memory
and number of tasks does seem to make sense give the issue you linked to.
I'll upgrade and see where that leaves the issue.
Thanks for your help!
--
Tom Arnfeld
Developer // DueDil
(+44) 7525940046
25
6 matches
Mail list logo
