VVV: Trusty64 not found

I’m using mac os v 10.12.1 - i removed the curl that was packaged with vagrant in /opt/vagrant/embedded/bin so that it would use the version installed by the os and it fixed the problem for me.

Yeah just ran into this issue, removing the Vagrant curl resolved it – sudo rm /opt/vagrant/embedded/bin/curl

Ditto for firecentaur’s note. I’m also Win7/x64 / vagrant 1.8.1 and got the same vague error message about “‘ubuntu/trusty64’ could not be found.” For me it was resolved by installing the VC10 x86 runtimes: https://www.microsoft.com/en-us/download/details.aspx?id=8328

Had to run

sudo rm /opt/vagrant/embedded/bin/curl

MacOS 10.12.1 Vagrant 1.8.7

How is this an issue from May 8, 2014 and still not resolved? Brand new computer with MacOS Sierra and executing sudo rm /opt/vagrant/embedded/bin/curl fortunately worked for me too.

Same here, on OSX Yosamite 10.10.5 (14F2009) - deleting the curl file fixed the vagrant up step

It seems I had the wrong box_url:

config.vm.box = "trusty64"
config.vm.box_url = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"

It’s working now.

Usinx OSX 10.11.6, I had the same problem and followed the suggestion of @knesbit to remove the vagrant version of curl, which fixed the problem.

sudo rm /opt/vagrant/embedded/bin/curl worked for me too.Thanks vagrant -v Vagrant 1.8.7

Needed to run this today (sudo rm /opt/vagrant/embedded/bin/curl) on OSX on Vagrant 1.8.7

Just installing VC ++ 2010 x86 has resolved my issue on win 8.1 with vagrant 1.8.4

was getting the same:

The box 'ubuntu/trusty64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/ubuntu/trusty64"]

but doing this as @wallnerryan commented fixed it for me,

sudo rm /opt/vagrant/embedded/bin/curl

@mkjonesuk Just ran into this same issue this morning! sudo rm /opt/vagrant/embedded/bin/curl fixed it for me too.

As suggested by @knesbit, removing vagrant’s curl fixes the issue on macOS Sierra (10.12.1). Thanks!

I tried everything. I was on fresh install of Windows 10 and Vagrant 1.9, so I downloaded curl for windows. I also removed the curl in C:/Vagrant/embedded/ . And like @robvdl suggested, I made sure I was downloading the right box. It finally worked. config.vm.box = “ubuntu/trusty64” config.vm.box_url = “https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box”

I am on El Capitan, sudo rm /opt/vagrant/embedded/bin/curl worked for me too. Thanks!

I’m on El Capitan, and removing the embedded curl worked for me as well.

Can anyone write this up for the wiki?

Did you try a vagrant destroy? That’s the recommended way to upgrade to 14.04. https://github.com/Varying-Vagrant-Vagrants/VVV/commit/b1764cec682058fdfd13e7ff32d1a68204a35822

You can also try vagrant box add ubuntu/trusty64. I haven’t tried it, but it should work.