Few things I would check are as follows:
* Do you have admin rights to the system?
* Can you try opening a powershell console as admin and use the following
command to start the installer:
msiexec.exe /i "c:\downloads\vagrant_1.8.1.msi"
Replace the path to where you have the msi file.
On
There are no other vagrant or VB processes running. I cleared out all the
VMs from VirtualBox & there are no disks shown in the Media Manager.
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in
Hello Alvaro,
Thanks for the reply. I've tried doing vagrant init and vagrant up and
vagrant init and it failed with a timeout message. The ruby error is
intermittent, it seems. The timeouts seem to be happening much more often.
However, this time, after running vagrant init and vagrant up,
Hello,
The message show there is some issue with certificates.
Do you know if you are behing a proxy (corporate proxy?) that use
certificates?
Alvaro
On Thu, Feb 4, 2016 at 9:08 PM, Kaushik Thanki <
kaushik.tha...@clariontechnologies.co.in> wrote:
> I m working Nylas sync - engine
>
>
cat host_vars/all
ansible_python_interpreter=/usr/bin/python2.7
at least for ansible, this is easy way.
On Thursday, February 4, 2016 at 11:12:41 AM UTC-8, pixel fairy wrote:
>
> ubuntu 15.10 no longer ships with python2, you have to install it. thats
> easy with a global provision.
>
> but,
For some reason the puppet provisioner doesn't work for me on AWS - not the
way I have my stuff set up.
I have to do an inline shell provisioner for my puppet apply when it's on
AWS, but I want to use my puppet provisioner on virtualbox.
I can't seem to find a value that I can do a
I m working Nylas sync - engine
https://github.com/nylas/sync-engine When i moved to step 4. vagrant up
It gives mentioned errors (in attached image) to me..
guys any idea in this regards... .?
--
This mailing list is governed under the HashiCorp Community Guidelines -
