Windows 8.1, latest vagrant and VirtualBox versions. Running commands in git CLI on Windows.
I was able to start up ubuntu/trusty64 without any problem, and did not need to log in to atlas.hashicorp.com.
But when I tried ubuntu/xenial64 I got an error.
vagrant init ubuntu/xenial64; vagrant up --provider virtualbox
Also, trusty 64 did not cause any waings about logging in with vagrant login, but since xenial 64 did cause such a waing, I immediately created an account at atlas.hashicorp.com.
I used vagrant login to log in, getting the message "You are now logged in."
I deleted the vagrant stuff from the folder and redid the init and up commands, but again I get the same error.
$ vagrant init ubuntu/xenial64; vagrant up --provider virtualbox
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the Idea in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/xenial64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'ubuntu/xenial64' 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/xenial64"]
Error:
But the "Error:" portion is blank.
Recent Questions...
ما را در سایت Recent Questions دنبال میکنید
برچسب:
نویسنده: استخدام کار
بازدید: 475
تاريخ: يکشنبه
23 خرداد
1395 ساعت: 9:48