-
Notifications
You must be signed in to change notification settings - Fork 11.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can not vagrant up #85
Comments
i have the same issue |
I've reported this issue to the general FSND issues page here: https://github.com/udacity/fsnd-issues/issues/117 Also describes a workaround there. |
The |
The best architecture is to use Vagrant for only installing Docker. Then, docker takes care of the rest (python, psql) .e.g Container FROM python and install psql. Following this architecture, students can use directly docker. |
I got issues and I fixed that by modifying the box from . |
I ran into this with Vagrant 2.0.3. It looks like the fix isn't necessary now, and |
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bento/ubuntu-16.04-i386' could not be found. Attempting to fin d and install...
default: Box Provider: virtualbox
default: Box Version: = 2.3.5
==> default: Loading metadata for box 'bento/ubuntu-16.04-i386'
default: URL: https://vagrantcloud.com/bento/ubuntu-16.04-i386
==> default: Adding box 'bento/ubuntu-16.04-i386' (v2.3.5) for provider: virtual box
default: Downloading: https://vagrantcloud.com/bento/boxes/ubuntu-16.04-i386 /versions/2.3.5/providers/virtualbox.box
default:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Failed to connect to vagrantcloud-files-production.s3.amazonaws.com port 443: Ti med out
The text was updated successfully, but these errors were encountered: