[vagrant-up] Re: Unable to connect to Vagrant private network from host

on guest ip addr show: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever

Re: [vagrant-up] Re: OSX 10.10: cannot access guest machine by private_network

>> netstat -anp | grep -i ':5000' tcp0 0 127.0.0.1:5000 0.0.0.0:* LISTEN 10070/node >> iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source d

[vagrant-up] Unable to connect to Vagrant private network from host

Hi all, I blocking a big issue: 1. vagrant version is 1.7.2, virtual box is the latest 2. I want to access guest web server from host by port forward, it failed.(time out) -> http://localhost:5050 3. Then I tried use private_network, but still failed. 4. There is my vagrantfile

Re: [vagrant-up] Re: Vagrant provision failed with message: machine is not ready for guest communication

Hello, does vagrant ssh-config looks correct ?? On Wed, Feb 18, 2015 at 9:13 AM, Anthony Kong wrote: > I turned on the debug flag and it is what I see. But as I mentioned I can > 'vagrant ssh' into the box > > DEBUG ssh: == Net-SSH connection debug-level log END == > INFO ssh: SSH not up: # a

Re: [vagrant-up] Problems with permission.

couple of options: change apache to run under vagrant create a user with same user id and group id of apache, put a password, and use that user for sftp On Tue, Feb 17, 2015 at 12:18 PM, Jorge Copia wrote: > Hi, I have a problem. I need upload files with php form and upload files > with sftp, m

Re: [vagrant-up] Vagrant Up...

Hello, does your network require proxy, or auth over proxy? the message is telling that the guest is failing to do name resolution. usually the guest will use a NAT card and use host for name resolution, here that seems not to be working. on the host can you do Windows: nslookup us.archive.

Re: [vagrant-up] Vagrant box list and vagrant global-status - different result

Hello are 2 different things.. vagrant box list will give you the list of templates vagrant global-status will give you the list of projects or Vms that have been created from a template + a Vagrantfile Example: on a new computer you do vagrant box add hashicorp/precise32 Vagrant box list wil

Re: [vagrant-up] Re: Issue with 2 public_networks

Hello, Why you need a MAC on the first one? What's the output of ifconfig -a on the 2nd boot ? On Thu, Feb 19, 2015 at 12:11 AM, John Economou wrote: > I have tried 2 ways: > > a. > config.vm.network "public_network", ip: "x.x.x.x", netmask: > "255.255.255.192", mac: "00", bridge:

Re: [vagrant-up] Empty Boxes for things like PXE provisioning?

can you share the final goal? Do you want to do a LAB of Vagrant or do you want to do a LAB of Foreman/puppet ? If the second is the goal, not sure if vagrant (a tool to deploy VMS from template) would be the right tool. With a script and virtualbox, you can create empty VMS and you will have m

Re: [vagrant-up] Re: vmware-workstation-plugin won't load

Hello, You should use the packaged from the formal Download site, and use the default path, yes. On Thu, Feb 19, 2015 at 8:02 AM, Matthew Versaggi wrote: > So exactly how does one fix that situation? > > I assume it's because I used apt-get install to install Vagrant on linux > when I should ha

Re: [vagrant-up] Text file busy @ unlink_internal

Hello, Can you share your Vagrantfile ? Whats your host OS ? On Fri, Feb 20, 2015 at 4:59 AM, Armando Godinez wrote: > I keep getting this: > > > > This happens when uploading files to my rails

Re: [vagrant-up] Looking for version 1.4.3 Documentation

On Fri, Feb 20, 2015 at 11:43 AM, Christopher Hahn wrote: > > The hardest part of this is likely the fact that I am stuck on an old > version. Hello Can you describe what you want to do? Vagrant on virtualbox by default give you eth0 as NAT then, if you add: config.vm.network "private_network

Re: [vagrant-up] Synced folders + multi machine read from YAML file issues inside Docker provider?

Hello, If you want a share to be present in all the docker, then you can do that machine first, and then the 2 or 3 docker containers will be able to mount them. in your Vagrantfile, can you check if this is correct: config.vm.synced_folder sync['host'], sync['guest'], :create => true, :mount_op

Re: [vagrant-up] New trusty64 URL?

That box is managed by canonical, no sure how to engage them On Fri, Feb 20, 2015 at 9:59 PM, wrote: > Hello, > > I am trying to download trusty64 for Refinery > (http://daeilkim.com/refinery.html), but the URL cannot be found. > > Is there a new URL? > > Many thanks. > > Philippe > > --

Re: [vagrant-up] Vagrant + openstack + CoreOS

What's the Vagrantfile you are using? please remove any user/pass detail On Sat, Feb 21, 2015 at 6:11 AM, Laurent Bertrand wrote: > Hi, > > When trying to use vagrant to launch a Core OS instance on Openstack using > user-data, I have the following error: > > ==> default: Configuring and enablin

Re: [vagrant-up] Re: OSX 10.10: cannot access guest machine by private_network

on guest: netstat -anp | grep -i ':5000' iptables -L On Sat, Feb 21, 2015 at 2:07 PM, Liu Wei wrote: > shutdown firewall. but still not working > > On Saturday, February 21, 2015 at 1:15:32 AM UTC+8, Vincenzo D'Amore wrote: >> >> or may be there is a firewall running on your guest. >> >> On Fr

Re: [vagrant-up] Re: OSX 10.10: cannot access guest machine by private_network

shutdown firewall. but still not working On Saturday, February 21, 2015 at 1:15:32 AM UTC+8, Vincenzo D'Amore wrote: > > or may be there is a firewall running on your guest. > > On Fri, Feb 20, 2015 at 6:10 PM, Vincenzo D'Amore > wrote: > >> may be you have already something on port 5000... >> Ha

Re: [vagrant-up] Re: OSX 10.10: cannot access guest machine by private_network

Thanks Vincenzo. I'm sure only VBoxHeadl use port 5000/5050 On Saturday, February 21, 2015 at 1:10:49 AM UTC+8, Vincenzo D'Amore wrote: > > may be you have already something on port 5000... > Have you tried: > > sudo lsof -iTCP -sTCP:LISTEN -n -P > > this command list the listen port on mac os x.

Re: [vagrant-up] vagrant push oddities

Hi, I'm trying to develop a deployment strategy for my team and we had recently started using Vagrant when I saw the announcement about push some months ago. It seemed like a good match. Now I'm finally getting around to doing it and the immediate problem I have is making the local-exec push

[vagrant-up] Vagrant + Ansible for Windows VM

I am trying to run Vagrant with Ansible on my Mac to create and provision a Windows 7 VM. I am able to "vagrant up" when I don't invoke Ansible in the Vagrantfile. I am using the following playbook.yml --- - hosts: all tasks: - name: run win ping win_ping: When I add the ansible

Re: [vagrant-up] Re: OSX 10.10: cannot access guest machine by private_network

or may be there is a firewall running on your guest. On Fri, Feb 20, 2015 at 6:10 PM, Vincenzo D'Amore wrote: > may be you have already something on port 5000... > Have you tried: > > sudo lsof -iTCP -sTCP:LISTEN -n -P > > this command list the listen port on mac os x. > > On Fri, Feb 20, 2015 a

Re: [vagrant-up] Re: OSX 10.10: cannot access guest machine by private_network

may be you have already something on port 5000... Have you tried: sudo lsof -iTCP -sTCP:LISTEN -n -P this command list the listen port on mac os x. On Fri, Feb 20, 2015 at 6:01 PM, Liu Wei wrote: > My Gist url https://gist.github.com/EricCat/0ee4e0c6c3138a2e0d8b > > On Friday, February 20, 201

[vagrant-up] Vagrant + openstack + CoreOS

Hi, When trying to use vagrant to launch a Core OS instance on Openstack using user-data, I have the following error: ==> default: Configuring and enabling network interfaces... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!

[vagrant-up] Re: OSX 10.10: cannot access guest machine by private_network

My Gist url https://gist.github.com/EricCat/0ee4e0c6c3138a2e0d8b On Friday, February 20, 2015 at 11:30:49 PM UTC+8, Liu Wei wrote: > > I use vagrant 1.7.2 on osx 10.10. > 1. Only use port forward: config.vm.network "forwarded_port", guest: > 5000, host: 5000, host machine cannot access guest w

[vagrant-up] Re: OSX 10.10: cannot access guest machine by private_network

I want to access this guest from host. Also I've tried port 5050 -> 5000 On Friday, February 20, 2015 at 11:30:49 PM UTC+8, Liu Wei wrote: > > I use vagrant 1.7.2 on osx 10.10. > 1. Only use port forward: config.vm.network "forwarded_port", guest: > 5000, host: 5000, host machine cannot access

[vagrant-up] OSX 10.10: cannot access guest machine by private_network

I use vagrant 1.7.2 on osx 10.10. 1. Only use port forward: config.vm.network "forwarded_port", guest: 5000, host: 5000, host machine cannot access guest with localhost:5000; 2. Set private_network: config.vm.network "private_network", ip: "192.168.33.10", still cannot access by 192.168.33.10:

Re: [vagrant-up] Re: Is there a way to set up a box repository inside the corporate network

Thanks Shawn, that was what I was looking for :-) Cheers, Torben On Thu, Feb 19, 2015 at 5:06 PM, Shawn Neal wrote: > You set the VAGRANT_SERVER_URL env var. > > At work we set this on all our dev machines (via Boxen) so we can add boxes > using the short notation 'mycompany/mybox'. The env var

[vagrant-up] New trusty64 URL?

Hello, I am trying to download trusty64 for Refinery (http://daeilkim.com/refinery.html), but the URL cannot be found. Is there a new URL? Many thanks. Philippe - D:\Users\philippe\Desktop\refinery\refinery>vagrant up Br

Re: [vagrant-up] How to conditionally setting config variables based on the Vagrant operation?

Hey Brian, You could probably parse ARGV for that, but that's really ugly and I wouldn't recommend it. Maybe the vagrant-triggers plugin is better suited for your use case? HTH, Torben Am 19.02.2015 23:07 schrieb "Brian D" : > Hi all, > > I'd like to conditionally set a variable based on the Va