Mike, I'll try to help you via StackOverflow thread.
Best regards, Gilles
Le jeudi 27 novembre 2014 17:36:27 UTC+1, Mike Thirlwell a écrit :
Also posted on Stack Overflow:
http://stackoverflow.com/questions/27174405/vagrant-cant-run-ansible-when-provisioning
I have created a Vagrantfile to
Same problem with Vagrant 1.7 under Windows 7. Tried with version 1.6.5 and
worked without problems.
El miércoles, 10 de diciembre de 2014 07:41:55 UTC+1, K. Lutrova escribió:
I'll admit, I am very lost on this. I heard about Vagrant and am
attempting to get something set up for testing to
Hello,
I'm getting something similar. Not installed vagrant on this laptop before
(OSX 10.9.5), ran the installer with
SHA 2b3d7cf0d2490e1f1d4f7ad13e2caf44a50cec33419a6ea281f3e5c693da7e8d
$ vagrant
/opt/vagrant/embedded/gems/gems/vagrant-share-1.1.2/lib/vagrant-share/
activate.rb:8:in
I'm pulling my hair out here. If I use the following config file I end up
with the following error:
Error while activating network: Call to virNetworkCreate failed: internal
error Network is already in use by interface br0.
I have a very basic Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby
Hi,
I recently purchased the VMWare plugin for Vagrant running v1.6.5
Will I need to re-purchase the plugin now that v1.7 is out?
Regards,
Mark
--
You received this message because you are subscribed to the Google Groups
Vagrant group.
To unsubscribe from this group and stop receiving emails
Mark,
Nope, you will never have to re-purchase the plugin for the Vagrant
version update. You may have to redownload it one day but not for this
version (and we've never broken backwards compatibility yet for the
plugin).
Best,
Mitchell
On Wed, Dec 10, 2014 at 8:25 AM, Mark Fletcher
Hi Mitchell,
Was this fix applied to the .deb pkgs? I see a similar issue when upgrading
from v1.6.5 to v1.7.0 on Ubuntu 14.10. Completely uninstalling vagrant and
then reinstalling the v1.7.0 deb pkg does not resolve this.
Thanks,
Mark
On Wednesday, 10 December 2014 01:16:06 UTC-6,
Mitchell,
Thank you for the quick response!
Best Regards,
Mark
On Wednesday, 10 December 2014 10:28:57 UTC-6, Mitchell Hashimoto wrote:
Mark,
Nope, you will never have to re-purchase the plugin for the Vagrant
version update. You may have to redownload it one day but not for this
Vagrant commands, including vagrant -v are returning.
C:\HashiCorp\Vagrant\embedded\bin\ruby.exe: No such file or directory --
C:/cygwin64/lib/vagrant/pre-rubygems.rb (LoadError)
I don't think I saw this with 1.6.x
Help me get past this? Otherwise, I'll try downgrading Vagrant.
Thanks,
FYI, the download was from roughly 2 hours ago.
On Wednesday, December 10, 2014 11:41:37 AM UTC-5, Jamie Jackson wrote:
Vagrant commands, including vagrant -v are returning.
C:\HashiCorp\Vagrant\embedded\bin\ruby.exe: No such file or directory --
C:/cygwin64/lib/vagrant/pre-rubygems.rb
Hi,
This is a different issue! I guess moving vagrant-login to core caused
more problems than we expected and didn't affect us locally since we
weren't devving on the installer. I'm working on this now. Sorry!
Best,
Mitchell
On Wed, Dec 10, 2014 at 8:36 AM, Mark Fletcher
Confirmed it works properly with 1.6.5. Will wait for a solution before
trying 1.7 again.
Thanks,
Jamie
On Wednesday, December 10, 2014 11:43:24 AM UTC-5, Jamie Jackson wrote:
FYI, the download was from roughly 2 hours ago.
On Wednesday, December 10, 2014 11:41:37 AM UTC-5, Jamie Jackson
I'm getting these errors on OS X 10.10.1 with vagrant 1.7 upgraded from
1.6.5
/opt/vagrant/embedded/gems/gems/vagrant-1.7.0/plugins/hosts/bsd/cap/nfs.rb:140:
warning: character class has '-' without escape: /^# VAGRANT-BEGIN:( 501)?
([\.\/A-Za-z0-9-_]+?)$/
Confirmed. There appears to be an issue with 1.7 on Windows. Installing
1.6.5 and testing that worked without any issue.
On Wednesday, December 10, 2014 4:30:43 AM UTC-5, Vicente Gallur Valero
wrote:
Same problem with Vagrant 1.7 under Windows 7. Tried with version 1.6.5
and worked without
What does Waiting for SSH to become available... actually mean? Is it
simply waiting for port 22 (or whatever is set) to be available?
My vagrant up process has stuck at this point a couple times. Debugging why
this is happening.
TIA,
-T
--
You received this message because you are
Yes! Thanks all of you for your input. I removed the port forwarding, added
the remote host IP, and removed the port from the browser window PHPStorm
opens and it works :)
--
You received this message because you are subscribed to the Google Groups
Vagrant group.
To unsubscribe from this
Are the Linux installers/packages also updated? I just(a few minutes ago)
downloaded the x64 deb package and it's giving me the same error.
Regards
Johan
On Wednesday, December 10, 2014 8:16:06 AM UTC+1, Mitchell Hashimoto wrote:
Marc,
This should now be fixed. Please redownload the
Your best option IMHO would be changing this section in your Vagrant file:
config.vm.provider virtualbox do |vb|
vb.gui = true
end
(if you're not using Virtualbox, it should be something similar)
The idea is to tell vagrant to display the UI of the VM manager, so you can
see what the machine
Hello Seth,
Here it is: http://pastebin.com/93WphVvW
Thanks for your help!
On Wed Dec 10 2014 at 4:11:21 PM Seth Vargo sethva...@gmail.com wrote:
Hey Rento,
Can you please include your Vagrantfile and the debug output? It might be
best to open a GitHub issue for this.
Best,
Seth
On
I have tried everything under the sun. For the life of me every time I do
`vagrant up` with dnsmasq turned off I get the following error and nothing
happens. However if I have dnsmasq turned on, I'll eventually get a
192.x.x.x IP assigned after about 40seconds. But this isn't accessible to
if anyone ever comes across this thread in the future, I just thought I'd
reply to say that I just found this:
http://phusion.github.io/traveling-ruby/
This looks like a good option.
On Wed, Nov 26, 2014 at 9:35 AM, Bethany Skurrie bskur...@dius.com.au
wrote:
Great, thanks for the pointers!
@TomDV
Can you point out exactly where that page talks about turning an .OVA file
into a .BOX file?
All I see there is talk about setting up a .BOX file.
On Saturday, 23 June 2012 09:09:35 UTC+9:30, TomDV wrote:
On 22 Jun 2012, at 17:14, Matteo Parmi wrote:
Hi,
is it possible to import
Seems is more a vagrant issue rather than a packer one.. so I am cc: the
vagrant mailing list.
vagrant for vmware is a paid plugin.. do you have it?
vagrant plugin list
if you do, that came with support, and instructions.. have you used before
or this is the first time?
Thanks,
Alvaro.
On
Hi everybody,
I was missing the public website for searching vargant baseboxes now
that http://vagrantcloud.com gets redirected to
http://atlas.hashicorp.com
However, I just found it. It's not directly linked on the atlas
homepage, but it still exists here:
Yes, this is a known bug with the installers.
See here:
https://github.com/mitchellh/vagrant/issues/4927
..and the referenced issues:
https://github.com/mitchellh/vagrant/issues/4924
https://github.com/mitchellh/vagrant/issues/4920
https://github.com/mitchellh/vagrant/issues/4919
- all the same
25 matches
Mail list logo
