Skip to content
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

Open
Sheldon3537 opened this issue Feb 7, 2018 · 6 comments
Open

can not vagrant up #85

Sheldon3537 opened this issue Feb 7, 2018 · 6 comments

Comments

@Sheldon3537
Copy link

$ 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

@HassanTC
Copy link

HassanTC commented Feb 9, 2018

i have the same issue

@SteveWooding
Copy link
Contributor

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.

@SteveWooding
Copy link
Contributor

The Vagrantfile has been updated with the workaround: https://github.com/udacity/fullstack-nanodegree-vm/blob/master/vagrant/Vagrantfile

@abdennour
Copy link

abdennour commented Mar 3, 2018

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.

@abdennour
Copy link

abdennour commented Mar 3, 2018

I got issues and I fixed that by modifying the box from bento/ubuntu-16.04-i386 to bento/ubuntu-16.04.

.

@ATMontague
Copy link

I ran into this with Vagrant 2.0.3. It looks like the fix isn't necessary now, and Vagrant::DEFAULT_SERVER_URL.replace('https://vagrantcloud.com') prevents vagrant up from working. I removed it and it works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants