Hello Jorge,
check this:
https://github.com/mitchellh/vagrant/issues/3493
On Thu, Nov 6, 2014 at 3:12 PM, Jorge Copia wrote:
> Hellow, I'm Jorge from Perú.
>
> I have install vagrant 1.6.5 in ubuntu 14.04. When I put any vagrant
> command, for example:
>
> In a empty folder:
> /home/user/vm
without seeing the line i can't comment.
On Thu, Nov 6, 2014 at 4:19 PM, Anthony Kong
wrote:
> Hi all,
>
> I am trying to vagrant up this vagrant file:
> https://github.com/sensu/sensu-chef/blob/master/examples/Vagrantfile
>
> Because the distribution is old, when the apt-get update is run, it t
Hi all,
I am trying to vagrant up this vagrant
file: https://github.com/sensu/sensu-chef/blob/master/examples/Vagrantfile
Because the distribution is old, when the apt-get update is run, it throws
a lot of error messages like
==> default: Err http://us.archive.ubuntu.com raring/main Sources
==
Hellow, I'm Jorge from Perú.
I have install vagrant 1.6.5 in ubuntu 14.04. When I put any vagrant
command, for example:
In a empty folder:
/home/user/vm/$ vagrant -v
It's create automatically these files:
d20141105-6068-y17u4w, vagrant20141105-6068-1g697wx1,
vagrant20141105-6068-1wtubuw2, va
I think this problem has to do with the way you are creating the box file.
You seem to be using the zip format rather than the tar format. If using
7za try using the -tar switch?
Rob.
On Wednesday, 22 October 2014 02:31:21 UTC+10, Jafar Soltani wrote:
>
> Hello,
> I have problems creating Win20
Jeff,
What was the bug? Having a very similar situation.
On Wednesday, October 1, 2014 4:04:26 PM UTC-4, Jeff MacDonald wrote:
>
>
> The folks @vagrant got back to me. Its a bug with the provider. Or a
> feature not implemented yet.
>
> Jeff.
>
--
You received this message because you are sub
by default most of the web servers do not index directories, you need to
modify the configuration file
example:
https://wiki.apache.org/httpd/DirectoryListings
Options +Indexes
On Wed, Nov 5, 2014 at 7:04 PM, Robert Stein wrote:
> I meant to write http://127.0.0.1:4567 that I am getting th
I did add a PR for the documentation to add this example since is quite
handy
https://github.com/mitchellh/vagrant/pull/4788
Alvaro.
On Thu, Nov 6, 2014 at 8:54 AM, Alvaro Miranda Aguilera
wrote:
>
> On Thu, Nov 6, 2014 at 1:10 AM, San wrote:
>
>> *config2.vm.synced_folder "./scripts", syncDi
I think it's related to networking. If I remove the private network option
from the Vagrantfile, it doesn't happen.
On Wednesday, November 5, 2014 2:56:32 PM UTC-5, Russ Egan wrote:
>
> I'm running into the same problem, but it doesn't appear to be because of
> the multiple CPUs. Happens even
I'm running into the same problem, but it doesn't appear to be because of
the multiple CPUs. Happens even with a single vcpu. I'm running with
fusion 7.0.1 on Yosemite, latest vagrant. The ssh config is only messed up
after the initial `up` command. If I shut down the VM and bring it up
aga
On Thu, Nov 6, 2014 at 1:10 AM, San wrote:
> *config2.vm.synced_folder "./scripts", syncDir+"/scripts", type: "rsync",
> rsync__exclude: "*.json", *
> * rsync__args:
> ['--verbose', '--rsync-path="sudo rsync"']*
Worked for me.
1. you hav
Typically they wont be.
A solution is to mount your database directory as a shared folder and so
that would be persistent across up and downs but it will be really slow. In
theory vagrant is used a a development / test area and as such you should
expect that at some point all of you data will go a
I am new to vagrant and slowly (very slowly) learning a bit about it.
I have added a box and I am able to access phpmyadmin from my browser.
If I vagrant destroy, will the databases I create/use be destroyed or will
they be there when I vagrant up?
If they won't be what is the proper use?
--
I think I already tried that before. But anyway, it still doesn't work.
So, this is in my Vagrant file now:
*config2.vm.synced_folder "./scripts", syncDir+"/scripts", type: "rsync",
rsync__exclude: "*.json", *
* rsync__args:
['--verbose'
14 matches
Mail list logo
