Closed wixyvir closed 5 years ago
What the output of vagrant --version
on your machine?
I just tested and it downloaded the box from https://vagrantcloud.com just fine.
@UtahDave You're right, looks like it works with Vagrant >= 2.0 but not with Vagrant < 2.0.0.
Where I got this issue:
cyprien.diot@techCyp:~/salt-vagrant-demo$ vagrant --version
Vagrant 1.9.2
But it works with Vagrant 2.0.4:
[root@021071bf715f work]# vagrant box add bento/ubuntu-16.04
==> box: Loading metadata for box 'bento/ubuntu-16.04'
box: URL: https://vagrantcloud.com/bento/ubuntu-16.04
^[[1;7BThis box can work with multiple providers! The providers that it
can work with are listed below. Please review the list and choose
the provider you will be working with.
1) hyperv
2) parallels
3) virtualbox
4) vmware_desktop
Enter your choice: ==> box: Waiting for cleanup before exiting...
==> box: Exiting immediately, without cleanup!
[root@021071bf715f work]# vagrant --version
Vagrant 2.0.4
On debian based distributions (like Ubuntu 17), Vagrant 2.0.4 is not yet available, so I still think this Pull Request is useful.
Thank you;
This works without any problems on Mac OS X 10.3.5, Vagrant 2.1.2, VirtualBox 5.2.16r123759.
Segue: I didn't know about Vagrant::DEFAULT_SERVER_URL.replace('https://vagrantcloud.com')
, not needed, but cool to know you wanted to use Artifactory or other custom repository.
@wixyvir
I'm getting this error:
[salt-vagrant-demo (wixyvir-fix_vagrant_server_url)]$ vagrant up
Vagrant failed to initialize at a very early stage:
There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.
Path: /home/me/repos/salt-vagrant-demo/Vagrantfile
Line number: 5
Message: RuntimeError: can't modify frozen String
My version of vagrant:
$ vagrant --version
Vagrant 2.1.5
Yes this is not compatible with Vagrant 2 anymore and all supported OS are now packaging Vagrant 2
Instead of atlas.hashicorp.com
Without this patch, you'll get this error: