Can't get past Getting Started with Vagrant

I get the VM running with the error:

deployingrails/first_box [] $ vagrant up
vagrant up
[default] Importing base box 'lucid64'...
[default] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.
Guest Additions Version: 4.1.16
VirtualBox Version: 4.1.18
[default] Matching MAC address for NAT networking...

This is, apparently, the warning mentioned in the VirtualBox Guest Additions section in the book. But when I try to follow the instructions I get a bunch of Could not resolve 'us.archive.ubuntu.com errors:

vagrant@lucid64:~$ sudo apt-get install dkms -y
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  fakeroot make patch
Suggested packages:
  make-doc diffutils-doc
The following NEW packages will be installed:
  dkms fakeroot make patch
0 upgraded, 4 newly installed, 0 to remove and 23 not upgraded.
Need to get 458kB of archives.
After this operation, 2,359kB of additional disk space will be used.
Err http://us.archive.ubuntu.com/ubuntu/ lucid/main make 3.81-7ubuntu1
  Could not resolve 'us.archive.ubuntu.com'
Err http://us.archive.ubuntu.com/ubuntu/ lucid/main patch 2.6-2ubuntu1
  Could not resolve 'us.archive.ubuntu.com'
Err http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main dkms 2.1.1.2-2ubuntu1
  Could not resolve 'us.archive.ubuntu.com'
Err http://us.archive.ubuntu.com/ubuntu/ lucid/main fakeroot 1.14.4-1ubuntu1
  Could not resolve 'us.archive.ubuntu.com'
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/m/make-dfsg/make_3.81-7ubuntu1_amd64.deb  Could not resolve 'us.archive.ubuntu.com'
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/patch/patch_2.6-2ubuntu1_amd64.deb  Could not resolve 'us.archive.ubuntu.com'
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/d/dkms/dkms_2.1.1.2-2ubuntu1_all.deb  Could not resolve 'us.archive.ubuntu.com'
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/f/fakeroot/fakeroot_1.14.4-1ubuntu1_amd64.deb  Could not resolve 'us.archive.ubuntu.com'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

I try to ping us.archive.ubuntu.com from within the VM and I cannot. But I can ping google.com and www.apple.com and ge.com (but not apple.com (w/out the www)) from w/in the VM.

FWIW the host can ping us.archive.ubuntu.com and every other domain name just fine.

sudo apt-get update fails as well for same reason. I have no idea how to proceed…

Looking at /etc/resolv.conf I notice it’s been populated with some nonexistant nameserver (there is no 10.0.2.3 machine, that I’m aware of, certainly not before Vagrant & VirtualBox rolled into town):

vagrant@lucid64:~$ cat /etc/resolv.conf 
nameserver 10.0.2.3
domain mydomain.com
search mydomain.com

I was expecting this book to be challenging but not to stump me on the very first steps…

BTW- Host is Mac OS X Lion (10.7.4)

appreciate any help!

I’m on OS X 10.6.8 and I get this on a new lucid64 box:

vagrant@lucid64:~$ sudo apt-get install dkms -y
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  fakeroot make patch
Suggested packages:
  make-doc diffutils-doc
The following NEW packages will be installed:
  dkms fakeroot make patch
0 upgraded, 4 newly installed, 0 to remove and 23 not upgraded.
Need to get 458kB of archives.
After this operation, 2,359kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main make 3.81-7ubuntu1 [166kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main patch 2.6-2ubuntu1 [121kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main dkms 2.1.1.2-2ubuntu1 [70.8kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main fakeroot 1.14.4-1ubuntu1 [101kB]
Fetched 458kB in 1s (353kB/s)   
Selecting previously deselected package make.
(Reading database ... 44864 files and directories currently installed.)
Unpacking make (from .../make_3.81-7ubuntu1_amd64.deb) ...
Selecting previously deselected package patch.
Unpacking patch (from .../patch_2.6-2ubuntu1_amd64.deb) ...
Selecting previously deselected package dkms.
Unpacking dkms (from .../dkms_2.1.1.2-2ubuntu1_all.deb) ...
Selecting previously deselected package fakeroot.
Unpacking fakeroot (from .../fakeroot_1.14.4-1ubuntu1_amd64.deb) ...
Processing triggers for man-db ...
Setting up make (3.81-7ubuntu1) ...
Setting up patch (2.6-2ubuntu1) ...
Setting up dkms (2.1.1.2-2ubuntu1) ...

Setting up fakeroot (1.14.4-1ubuntu1) ...
update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode.

vagrant@lucid64:~$ ping  us.archive.ubuntu.com
PING us.archive.ubuntu.com (91.189.91.24) 56(84) bytes of data.
64 bytes from ragana.canonical.com (91.189.91.24): icmp_seq=1 ttl=63 time=26.8 ms
64 bytes from ragana.canonical.com (91.189.91.24): icmp_seq=2 ttl=63 time=30.2 ms

I do have that same nameserver in the VM’s /etc/resolv.conf:

vagrant@lucid64:~$ cat /etc/resolv.conf 
nameserver 10.0.2.3

What’s in your Vagrantfile?

I’m getting a new laptop tomorrow (woo-hoo!) with Lion on it, I think… I’ll see if I run into the same issue you’re seeing.

Same symptoms here, had no connectivity from within the VM. Searching around online yielded this post from the Vagrant google group: t…

In short, you’re instructed to:

- uninstall both vagrant and virtualbox by issuing $ sudo apt-get remove vagrant virtualbox* && sudo apt-get autoremove && sudo apt-get autoclean
- download vagrant and virtualbox *.deb files from official websites and install first vagrant and then virtualbox.

I’m not using a Mac, but instead I’m on Ubuntu 12.10 64-bit. Maybe this will help you?

Cheers!