opt/vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/up/command.rb:58:in `execute' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment.rb:265:in `synchronize' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment.rb:266:in `block in batch' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment.rb:266:in `tap' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment.rb:268:in `block (2 levels) in batch' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/up/command.rb:67:in `block in execute' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/v2/command.rb:174:in `with_target_vms' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/v2/command.rb:174:in `each' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/v2/command.rb:192:in `block in with_target_vms' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/v2/command.rb:168:in `block in with_target_vms' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment.rb:537:in `machine' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/vagrantfile.rb:45:in `machine' Please use a provider that exists.ĮRROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/vagrantfile.rb:119:in `machine_config' Jason ERROR vagrant: Vagrant experienced an error! Details:ĮRROR vagrant: The provider 'aws' could not be found, but was requested toīack the machine 'default'. Below is the full error message, in case it is useful. I am really stuck on this, and I don't know what to do next. However this does not fix the error, and vagrant says it is deprecated anyway. When I google for this error, the only advice I get is to add vagrant.require_plugin 'vagrant-aws' I have verified that the aws plugin is installed, with $ vagrant plugin list I can successfully deploy to DigitalOcean, but with AWS I get the error: The provider 'aws' could not be found, but was requested toīack the machine 'default'. Wait for the confirmation that all resources have been destroyed.I am using Vagrant 1.6.5 and trying to deploy to Amazon AWS. Destroying the Environment įrom the quickstart/rancher/vagrant folder execute vagrant destroy -f. For more information, see Creating Deployments. Result: Rancher Server and your Kubernetes cluster is installed on VirtualBox. The default user/password is admin/admin. Once provisioning finishes, go to in the browser. To initiate the creation of the environment run, vagrant up -provider=virtualbox. Change the password of the admin user for logging into Rancher.Change the number of nodes and the memory allocations, if required.Go into the folder containing the Vagrantfile by executing cd quickstart/rancher/vagrant. Vagrant plugin install vagrant-vboxmanageĬlone Rancher Quickstart to a folder using git clone. Install them with the following commands: Vagrant will require plugins to create VirtualBox VMs. Virtualbox: The virtual machines that Vagrant provisions need to be provisioned to VirtualBox.Vagrant: Vagrant is required as this is used to provision the machine based on the Vagrantfile.For comprehensive setup instructions, see Installation. These guides are not intended for production environments. Note: The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. The following steps quickly deploy a Rancher Server with a single node cluster attached.
0 Comments
Leave a Reply. |