1

Can't SSH into a Vagrant Virtual Machine

view story
linux-howto

http://serverfault.com – Local Vagrant machine installed at ip address 10.0.0.23 and hostname lamp-vm. Using vagrant ssh I can connect just fine and do everything I need. This creates an ERROR - ssh vagrant@lamp-vm -v -v and I get debug1: connect to address 10.0.0.23 port 22: Connection timed out ssh: connect to host lamp-vm port 22: Connection timed out My etc/hosts file contains 10.0.0.23 lamp-vm. My .ssh/config file looks like Host lamp-vm User vagrant IdentityFile ~/.ssh/vagrant I have tried the ssh command with and without the -i /path/to/.sh/identity_file as well. How do I connect to my Vagran (HowTos)

grtyyu's picture
Submitted by grtyyu on 10/23/2012

Stories similar to Can't SSH into a Vagrant Virtual Machine

I have set up vagrant-dns but it's a shame I can't use the names from within my Vagrant VMs. (vagrant-dns sets up a nameserver on port 5300 on the host machine)

I found the resolver cookbook and it occurred to me I could maybe use that with Vagrant's port forwarding to make the vagrant-dns nameserver accessible from with the VM.

Vagrant / puppet workflow 50 weeks 16 hours ago

I'm new to puppet and vagrant, but I'm developing my own Puppet manifests intended to set up a vagrant box. That is, the puppet manifest is in my Vagrant directory on the host machine, and vagrant is invoking puppet -- there is no puppet server.

The thing is, my workflow is:

while(not working as desired) { vagrant destroy amend manifest vagrant up }

...

Routing a host to Vagrant 17 weeks 6 days ago

Vagrant

I currently have a set up on my development computer that uses apache and the hosts file to point to different folders. I's worked great but I've just discovered vagrant.

I'm following a tutorial to set up vagrant (a tool to build and configure portable virtual machine images), and it seems that vagrant documentation suggests using IPv4 address 33.33.33.10 to configure a new box.

That is a publicly routed IP adress, so I'm a bit confused why using this address is suggested. Since I don't own this network, I should not use an address from the 33.33.33.10/8 range.

I'm following a tutorial to set up vagrant (a tool to build and configure portable virtual machine images), and it seems that vagrant documentation suggests using IPv4 address 33.33.33.10 to configure a new box.

That is a publicly routed IP adress, so I'm a bit confused why using this address is suggested. Since I don't own this network, I should not use an address from the 33.33.33.10/8 range.

I am having trouble getting NFS setup on with vagrant:

On my local machine I have installed NFS:

apt-get install nfs-common nfs-kernel-server

And in my Vagrantfile set it to be used:

config.vm.share_folder("v-root", "/vagrant", ".", :nfs => true)

On vagrant up I get:

exportfs: /home/<user>/path/to/dir does not support NFS export

Mounting NFS shared folders failed.

This is a follow on to my previous question Vagrant Getting Started gives getaddrinfo: Temporary failure in name resolution.

I am running a fresh install of Lint Mint Nadia (14). I am following the instructions on Vagrant: Getting Started but have gotten stuck on the Provisioning.

New user to Ubuntu (Having Ubuntu 12.10 installed) and willing to start and develop using it.

Therefore I've installed Vagrant, Downloaded lucid64.box, initialized, started up and accessed by ssh.

to the test the internet connection on my client I've used the simple ping google.com and received unknown host: google.com.

I am trying to create a simple LAMP through Vagrant that can support multiple websites stored in /var/www. That can be done with vhosts.

Each project should end in .dev

Cant stand the idea creating each build that supports one project with a database each.

I cant make head or tails with Puppet or Chef.