----- Original Message ----- > From: "Max Rydahl Andersen" <[email protected]> > To: "Shubham Minglani" <[email protected]> > Cc: [email protected], "Saleem Ansari" <[email protected]> > Sent: Monday, February 15, 2016 1:18:25 PM > Subject: Re: [Container-tools] Query on mounted volumes being inaccessible > between host and guest - ADB Issue #118 > (Blocker) > > >>> Pros: > >>> - Maintained by Vagrant, so easier to maintain. Also, this will have > >>> more testing and user feedback backing it than our customized > >>> vagrant-sshfs plugin will have. > >>> - Works out of the box, just one `vagrant up` > >>> - No tinkering required on the Windows host (but NFS server required > >>> on Linux and Mac hosts) > >> > >> Mac has smb built in afaik. don't know about NFS - but if users need > >> to > >> install it this feels doomed since > >> we already have a ton of other things that need to be configured. > > > > Vagrant configures everything on the host, be it SMB or NFS, no > > configuration required. > > I'm confused - "but NFS server required on Linux and Mac hosts" implies > to me that you > or the user will need to do some install or setup (i.e. configuration) > for this to work ?
Oh, I'm sorry I could not convey the context fully. The gist is, no one configures any server, we just mention what we want to use and Vagrant does it! I included this point since I do not know how this is achieved on an OS X host. nfs-utils (which contains the NFS server) is installed as a dependency to vagrant-libvirt, so if vagrant is being run, the NFS server was already installed and configured by Vagrant. I 'assume' something like this also happens on an OS X based host too! (didn't test on one but some googling shows that it has an NFS server and Vagrant does use it.) Regards, Shubham _______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
