Hi Paul,
which VirtualBox Version do you have? After updating to 4.3.20 I
noticed that that VirtualBox suddenly started spawning 3 processes for
each VM. This was annoying and I had some not really reproducible
hickups. After swiching back to 4.3.12 everything worked again (and
also only 1 process
The bad interpreter error comes because after the shebang there is a ^M in
windows files which throws bash off.
The gem error points to a mixup between Ruby installations but I don't see
anything that would cause it in the path.
Usually this sort of thing happens to me when there are several embed
Hello,
You sent an screeshot of an app
I assume you run an app, and from the app you run vagrant up
?
open git bash -> open phpfun -> run vagrant from phpfun (that is
running from git bash)
no admin, just plain user.
Alvaro
On Sat, Mar 28, 2015 at 2:58 PM, Paul Lukitsch wrote:
> Do you mean
Do you mean try and run "vagrant up" for the phpfun vagrant folder (its the
hostname I'm using for that machine as well)?
Should I run git bash with admin rights or not?
P
On Friday, March 27, 2015 at 7:19:47 PM UTC-5, Alvaro Miranda Aguilera
wrote:
>
> Ok, lets try the workaround first, th
Ok, lets try the workaround first, then we can go to the formal explanation.
Can you run phpfun from the git bash ?
On Sat, Mar 28, 2015 at 1:10 PM, Paul Lukitsch wrote:
> There is an admin escalation during install of Vagrant, and then when you
> run "vagrant up", but you may be rightand i
Yeah, used to be 1, now are more.. that freak out many people.. but it's ok.
On Sat, Mar 28, 2015 at 1:18 PM, Paul Lukitsch wrote:
> Just another question as it seemed odd...
>
> While I don't usually check the task manager when I am using virtualbox
> normally (as in not headless), when I am ru
Just another question as it seemed odd...
While I don't usually check the task manager when I am using virtualbox
normally (as in not headless), when I am running a vagrant instance, there
are five different processes of VBoxHeadless running. They all seem
identical. This seems like a lot of
There is an admin escalation during install of Vagrant, and then when you
run "vagrant up", but you may be rightand it doesn't require admin
rights after the first time you run it, i.e., after vbox has already been
setup for the first time. In that case I am running "vagrant up" in an
admi
Hello,
I use Windows, vagrant + virtualbox as normal user.
Other than during install or when you create a new Virtualbox network
segment, it doesn't require UAC or pop ups.
That is with the normal UAC configuration.. not sure if you are under
an Microsoft Active Directory environment and they ha
One additional item: When I install vagrant, I am prompted two times to
authorize administrator privileges by UAC. Is this normal? Because you
seem to imply that I don't need to install it as Admin, yet that is how the
installer proceeds... The second authorization is to install some .msi wit
Thank you for your reply I did get it to work after uninstalling
everything and then reinstalling it but installing vbox after Vagrant. But
that seemed like dumb luck success...but at least "vagrant up" was working
and I had my environment.
However, I then tried to run/configure Vagrant in
Hello,
Vagrant just run fine as your user, so no need to become administrator.
delete c:/hashicorp and in your home delete .vagrant.d
once that is done, log out, log in.. and as your user, install vagrant
After the installation, you are ask to reboot, do that.
and in the next reboot, you shoul
On my Windows 7 Ultimate laptop, I had Vagrant, and a couple of development
environments working just fine... This wa sabout a week ago, and then
either virtualbox or Git released an updated version... Then things seemed
off, so I decided to uninstall everything (virtualbox, Vagrant, Git, and
13 matches
Mail list logo
