Hello!
I have following code in Vagrantfile:
config.vm.define :master do |master|
master.vm.box = centos64
master.vm.provider :virtualbox do |v|
v.name = virtual-tests-vm-node1
v.customize [modifyvm, :id, --memory, vm_mem]
end
master.vm.hostname =
is your host linux? to me, is running in your host not on the guest.
On Thu, Apr 24, 2014 at 8:19 PM, Вячеслав Артюхов artyukho...@gmail.comwrote:
Hello!
I have following code in Vagrantfile:
config.vm.define :master do |master|
master.vm.box = centos64
master.vm.provider
I'm using the hashicorp/precise64 box, and using the Docker provisioner.
I understand that I can issue some print statements (and am doing that).
When developing dockerfiles, each step is cached so that if there is an
error, you can essentially fix the error in the Dockerfile and more or less
I have a CentOS 5.x VM running on VMWare Fusion 6.0.3. After enabling
v.gui=true, I can see that the VM boots, however, Vagrant 1.5.4 seems to be
hanging at the Waiting for the VM to finish booting... step.
Here's the error that I keep seeing in the debug:
INFO ssh: SSH not up:
Any update on this subject? Just, could you find a way to solve it?
BR,
Em segunda-feira, 3 de junho de 2013 10h59min50s UTC-3, Just Anidiot
escreveu:
On Thursday, May 30, 2013 3:42:17 PM UTC-4, Just Anidiot wrote:
In general I have two host-only networks defined in virtualbox, vboxnet0
Hi all,
Since 3 days I have a problem with my Vagrant *OR* Win8.1.
It is not more possible to open my local vagrant domains in browser.
All my browsers (here its the chrome message) show the follow message:
Ups! Google Chrome konnte keine Verbindung zu dev.my-vagrant-project.de
herstellen.
In
I decided to play with Vagrant and Hyperv by creating an image of Ubuntu
13.10 server. After following the directions on how to export and package
it (placed zip on Google drive) and create the metadata.json file pointing
at the zip I then registered it with Vagrant Cloud
For the record I installed the latest gem from source. It appears they
fixed the issue with the error messages.
However it now appears that I am getting the following error:
INFO warden: Calling IN action:
Hi,
Note: I try to post my answer a third time, but I am suffering from a
very annoying anti-spam filter problem (the two deleted messages are mine,
mitchellh is aware of that problem, sorry for the noise)
*I'm asking for the `vagrant` user to not be created and instead a user
account with a
Hey guys, I'm having an interesting issue that I can't seem to fix with the
latest version of Vagrant (1.5.4). When I issue a vagrant up command,
with a valid Vagrantfile, even a barebones Vagrantfile with 4 or less
lines. I keep getting the following
your error is coming from:
vagrant-berkshelf-1.3.7
can you remove it?
On Fri, Apr 25, 2014 at 11:24 AM, Knox L gonzoliv...@gmail.com wrote:
updated paste bin, stack trace was cut short http://pastebin.com/u1PFiy5z
On Thursday, April 24, 2014 4:18:25 PM UTC-7, Knox L wrote:
Hey guys, I'm
On Fri, Apr 25, 2014 at 3:15 AM, Mario Linz geli...@gmx.de wrote:
192.168.56.105
I can reply in Spanish? will that work? :)
what happen is you do
http://*192.168.56.105 *
*?*
--
You received this message because you are subscribed to the Google Groups
Vagrant group.
To unsubscribe from
docker use layers, vagrant doesn't
so, if you first vagrant up, you have
vagrant provision
vagrant reload --provision
vagrant up --provision
etc,
in my particular use case, some commands like update rpms, I can run them
more than one, nothing happen
others, I just include some checks,
I did, thanks. That seemed to be the issue.
On Apr 24, 2014, at 17:47, Alvaro Miranda Aguilera kiki...@gmail.com wrote:
your error is coming from:
vagrant-berkshelf-1.3.7
can you remove it?
On Fri, Apr 25, 2014 at 11:24 AM, Knox L gonzoliv...@gmail.com wrote:
updated paste bin,
I ran into this same issue - using vagrant 1.5.4 and vmware fusion 5.0.4.
Just curious if you were able to figure out a fix for this...
An error occurred while executing `vmrun`, a utility for controlling
VMware machines. The command and output are below:
Command: [start,
I probably wasn't very clear. I meant to ask, how can I test a box before
I release it?
Is there any way to basically install a box from my HD using the
metadata.json and zip files or do you have to release/publish it?
- Jeremy
On Thursday, April 24, 2014 7:49:56 PM UTC-5, Alvaro Miranda
16 matches
Mail list logo
