![]() opt/vagrant/bin/./embedded/gems/gems/vagrant-1.6. opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment.rb:292:in `cli' opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/cli.rb:42:in `execute' 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 `batch' 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' Essentially, it is a layer of software installed between a virtualization tool (such as VirtualBox, Docker, Hyper-V) and a VM. opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/v2/command.rb:174:in `with_target_vms' Vagrant is an open-source tool that allows you to create, configure, and manage boxes of virtual machines through an easy to use command interface. ![]() opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/v2/command.rb:174:in `each' I have verified that the aws plugin is installed, with vagrant plugin list vagrant-aws (0.5.0) vagrant-digitalocean (0.7.0) vagrant-login (1.0.1, system) vagrant-share (1.1.1, system) When I google for this error, the only advice I get is to add vagrant.requireplugin vagrant-aws to the start of the Vagrantfile. 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:192:in `call' 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'. The below example shows how to specify SSD discs (gp2) for an 8GB volume that will be deleted when the machine terminates: aws.I am using Vagrant 1.6.5 and trying to deploy to Amazon AWS. You can specify the volume type in your VagrantFile using the block_device_mapping parameter in conjunction with VolumeType. General Purpose SSD is now the AWS default volume type (though when I was provisioning via Vagrant, it was creating Magnetic volumes if no specific parameters were set in the VagrantFile). When provisioning a machine in AWS, you are able to specify whether to use Magnetic, General Purpose SSD or Provisioned IOPS SSD volumes, depending on where you want to be on the performance/cost curve. The Vagrant AWS Provider allows you to use Vagrant to provision virtual machines in AWS.
0 Comments
Leave a Reply. |