Hi Alvaro: thank you for your response. It's the second case, the final goal is I want all local users to use the same VM. I didn't know about the VAGRANT_HOME variable, that should definitely help with sharing the base box and template.
If I set the VAGRANT_HOME var to a shared path, will the VM be also created there or do I have to set that in the VirtualBox environment explicitly? Thank you, Pp On Thursday, April 25, 2019 at 11:41:58 AM UTC-4, Alvaro Miranda Aguilera wrote: > > hello > > not sure I do understand where is the problem, so let me address 2 > scenarios. > > You want to have a VM available over the network, why you creating one, > and share it over the network, ppl can access as user/pass ip ? > > otherwise, you want to have local users using the same template and not > download this all the time, etc. > > If thats the case multiple options: > > 1 - config.vm.box_url = "file:///path/file.box" will do the trick. > > 2 - have a variable VAGRANT_HOME= to a common path, then all the users > will get the same box from the same template > , so each user can do `vagrant up` and will consume the same template. > > > Otherwise, can you explain more ? > > thanks > alvaro > > On Thu, Apr 25, 2019 at 12:10 AM Pepe Kubon <[email protected] > <javascript:>> wrote: > >> Hi: >> >> Wondering if somebody could help me with the following use case. >> >> I've got a Ubuntu 18 host set up for multiple users and want to install a >> Win 10 guest on it but just as a one box shared among all the users. >> Obviously, not at the same time, only one user would be logged in at a >> time. That way a new user could just be added to the Win guest and have >> immediate access to the current development environment on that machine. >> >> We're running VirtualBox as a provider. I thought maybe I could just move >> the disk VMDK to a shared location after the machine is created for the 1st >> user but that doesn't work. >> >> So, to my questions: >> >> 1) is there any vagrant setting out of the box that I'm missing that >> would allow me to do this? >> 2) if not, any suggestions on a workaround how to achieve this? >> >> Any help is much appreciated. >> >> Thank you, >> >> Pp >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/c9db2fa3-cc7a-4ec3-a132-e600fd4379e1%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/c9db2fa3-cc7a-4ec3-a132-e600fd4379e1%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Alvaro > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8c798dd6-ae14-4c96-b343-3252f787cf5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
