Hello,
The first thing is to check if your installation is healthy.
mkdir precise64
cd precise64
vagrant init -m hashicorp/precise64
vagrant up
If that works, then your Vagrant + Virtualbox installation is fine,
and we can think the project you are trying to use has some
requirements or issues.
Hello.
YEs, those can be deleted. Your guess is correct. Those were temp data
for a box download.
Alvaro.
On Tue, Nov 24, 2015 at 12:54 PM, Layla Sian wrote:
> hi-
> currently inside .vagrant.d\tmp I have 2 files, all called "box" followed by
> a hash like
Hello,
That error (from the subject) can happen in several cases.
- When you copy a folder and that include a .vagrant folder, you can
delete the folder and do vagrant up and that will create a new box.
This apply to projectd where they don't ignore this folder.
- You have some shared folder
Hello.
What;s your error, how you got there?
Alvaro.
On Tue, Nov 24, 2015 at 1:11 AM, sagar badhe wrote:
> Hi All,
>
> I am also getting same error for windows 7. Can you please suggest what to
> do to resolve this ?
>
> Regards
> Sagar
>
> On Wednesday, 5 November 2014
Hello, the url has an standard way to authenticate
http://user:password@server:port/path/path/file.extension
Give it a try and use the password from a ENV Variable.
Will this work?
Alvaro.
On Mon, Nov 23, 2015 at 6:53 PM, wrote:
> Hello All -
>
> I have been using
Hi Thomas,
if, as per my understanding, you are going to this for commercial purposes,
then point 3.a or 3.b are the answer to your problem. In the latter case
you will be even allowed to charge the end user for the hosting cost.
Alternatively I would recommend you to either contact the Canonical
Hi, I am encountering SSH error when doing Vagrant up. See the instructions
here: https://github.com/dnafrance/vagrant-hadoop-spark-cluster
Error log:>>
/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in
`block (2 levels)