try with
vagrant init hashicorp/precise64 if you want to download the machine from
Vagrantcloud
otherwise the issue is he doesn't know where to find that precise64
if you are reading some documentation, before 1.5.x came out, the
Vagrantfile required a box for box name and box_url to point
Hi!
After dropping an recreating the pagefile several times and different ways
(different drives, fixed vs. system managed, sizes) the error goes away.
The only change is to use the recommended size as fixed size instead of
using some size above this recommandation.
Kind regards
--
Alvaro,
That's not really a part of this use case. We'll be providing the boxes to
our dev team internally and will not be hosting them in the Vagrant Cloud.
On Wednesday, April 2, 2014 3:44:03 AM UTC-5, Alvaro Miranda Aguilera wrote:
if you host the box in vagrant cloud, you can hace thar, 1
Hi,
I've had this issue too, and suspect it's a bug with VirtualBox 4.3.10.
Regards
—
Ronan Amicel
On mer., avr. 2, 2014 at 4:22 PM, Bogdan B
bog...@the-noob.me=mailto:bog...@the-noob.me; wrote:
Since upgrading to 1.5.1 and VirtualBox to 4.3.10 I'm having a lot of problems
with
There is/was a huge issue with plugins too. If you’re using the plugins
vagrant-hosts
vagrant-pe_build
then your vagrant will stop working properly. I had to roll back to 1.4.3 and
have to remain there until Vagrant or the plugins or both get updates to start
working again. When you’re
hello
ah well
in that case
you need to import the box first like
vagrant box add name name.box
so when you do vagrant init name, it will create an initial vagrantfile
that have
config.vm.box = name
if you have the box in a internal server, you can distribute the
Vagrantfile, and include
Hi All,
I'm trying to write a provision script to install anaconda. I've managed to
run the installer properly, but since it's adding another version of python
on top of the VM python, I have to edit the PATH variable such that the
anaconda directory is first. I tried adapting this
On Thu, Apr 3, 2014 at 9:20 AM, Sean Easter sean.m.eas...@gmail.com wrote:
PATH=/home/vagrant/anaconda/bin:$PATH
i am a bit lost, I am asuming, your scripts are running as root and it's
fine, and then, you want to execute some commands as vagrant user
the script is run as root, if you want to
On Wed, Apr 02, 2014 at 05:49:50AM -0700, Richard Boyd II wrote:
That's not really a part of this use case. We'll be providing the boxes to
our dev team internally and will not be hosting them in the Vagrant Cloud.
As far as I'm aware, there isn't a publically-available implementation of
the
