Hi Lopez,
First of all Thanks for the plugins you developed. I came across this
plugin recently and found it to be very interesting and exactly suits our
requirement for an internal project. We would liket o take this forward and
enhance it (and contribute back). Couple of questions I have
*
Hi Alvaro,
thanks, but I believe it's a VirtualBox issue, not Vagrant (as I
didn't change vagrant but updated virtualbox).
And I bet it's Windows specific, too.
Just wondering whether other windows users are seeing such behaviour too...
Cheers,
Torben
On Fri, Jan 30, 2015 at 11:24 PM, Alvaro
hello
if you want them locally to the new deploy, you should put them inside the
vm..i think will be the easiest thing to do
will be compressed and available of first boot.
you may also try zip those files, include them with the vm at package time,
and they will be available at ~/.vagrant.d/boxe
hello, not sure if this is related to the same
but can you try
on the guest: mount
then on the host
vagrant reload --provision
and see if works or not? and compare the mounts available?
it seems that some folders are calculated for provisioner, and then don't
get mounted in a reload without pr
Hello, I have one per VM.
YEsterday or so, was an email of someone saying that after upgrade some
things like provisioners were being started twice (or 3?)
perhaps quicker delete the vagrant folder and reinstall ??
rm -fr /Applications/vagrant/
On Sat, Jan 31, 2015 at 8:31 AM, Torben Knerr
wr
Hi everybody,
after uprading to VirtualBox 4.3.20 I got some hangs when the VM was
booting.
Looking at the task manager I see three(!) VBoxHeadless.exe processes being
spawned every time I `vagrant up` a single Vagrant VM.
Screenshot here:
https://pbs.twimg.com/media/B8noW3jIcAApLSB.png:large
Hi Everyone, first at all I'd like to say congratulations for those who are
participating on the great Vagrant stuff, this has been very useful on my
day to day, now let's talk about the issue I have been seeing this since
upgrade from vagrant 1.7.1 to 1.7.2,
All time I make a vagrant reload I
When packaging a vagrant box, the package.box file does not contain a
synced folder /src that has a bunch of repos I downloaded to it during
provisioning. What would be the best way to include the synced folder so I
can distribute the vm?
--
You received this message because you are subscribed
