I'm not sure at this point if these are problems, but upon doing vagrant up I get a variety of warnings that seem to relate to this:

stdin: is not a tty

In particular, I get a number of these:

dpkg-preconfigure: unable to re-open stdin: No such file or directory

I also get a (strangely formatted, with extra linebreaks amongst the characters in curl) error, though other network connections via apt-get seem to work:

curl: (6) Couldn't resolve host 'get.docker.io'

Then I get the following issues, which seem fairly fatal:

/tmp/vagrant-shell: 16: [: 
root: unexpected operator

cp: 
cannot stat ‘./*’
: No such file or directory

Could not open requirements file: [Errno 2] No such file or directory: '/usr/local/etc/jiffylab/webapp/requirements.txt'
Storing complete log in /root/.pip/pip.log
stop: Unknown job: dockerd
start: Job failed to start
chown: 
cannot access ‘/usr/local/etc/jiffylab/webapp/’
: No such file or directory

/tmp/vagrant-shell: 36: /tmp/vagrant-shell: 
docker: not found

So, I'm guessing the failure to fetch docker is fatal. I don't know why that's happening, while other network access appears to work fine...

If it matters, I'm on VBox 4.2.16, vagrant 1.2.4, OS X 10.8.4. I've ssh'd into the virtualbox (with vagrant ssh) and there does seem to be a problem using curl for get.docker.io. As I said, it resolves fine from the host OS, and a host get.docker.io also resolves from within the vbox. You can't use that IP address directly with curl, though, as S3 demands something more textual.