Trusty64 box not downloading

[drawcard]

Expected Behavior

Running VVV for the first time, Trusty64 box should download from Hashicorp's servers.

Current Behavior

It does not appear to be doing this.

Possible Solution

Unknown

Steps to Reproduce (for bugs)

1. Follow VVV installation instructions
2. Run vagrant up

Error message:

I can fetch other boxes from Hashicorp, and other VM's work fine eg Scotch Box and Trellis.
I have also tried this idea: hashicorp/vagrant#7997 which deletes the broken curl package but still doesn't fix the problem.

Context

Your Environment

• VVV version: Latest from master branch
• Vagrant version: 1.9.5
• VM Provider name: Virtualbox
• VM Provider version: 5.0.x
• Operating System and version: macOS 10.12.1, 24GB disk space free

[drawcard]

Have also tried:

• vagrant box add trusty64 ubuntu/trusty64
• sudo rm -f /opt/vagrant/embedded/bin/curl

[drawcard]

For the time being I'm using another trusty64 box:

$ box add trusty64 https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box

$ vagrant box list
...
trusty64            (virtualbox, 0)

Edit line 150 of Vagrantfile:

 config.vm.box = "trusty64"

Then:

$ sudo vagrant up

[JJJ]

I can't reproduce this on a fresh VVV setup, with latest Vagrant & VirtualBox versions.

FWIW, after installing all optional Vagrant plugins, my box ritual usually looks something like:

vagrant destroy
vagrant box update
vagrant box prune
vagrant up

[LoreleiAurora]

That is the same box we use just not downloaded through the hashicorp api.

Your install appears to be using bento/ubuntu-14.04 as opposed to ubuntu/trusty64.

Can you please tell me what commit you are on?

[drawcard]

The commit I'm using is 4d1fb6f

[tomjn]

@drawcard does this still happen with Vagrant 2.0?

[tomjn]

I'm going to close this for now, if this is still an issue with 2.1 and the latest vagrant+virtualbox feel free to reopen

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.