vagrant-lxc 0.0.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +29 -0
- data/.gitmodules +3 -0
- data/.rspec +2 -0
- data/.travis.yml +8 -0
- data/.vimrc +1 -0
- data/Gemfile +19 -0
- data/Gemfile.lock +89 -0
- data/Guardfile +34 -0
- data/LICENSE.txt +22 -0
- data/README.md +209 -0
- data/Rakefile +5 -0
- data/bin/vagrant-lxc +9 -0
- data/boxes/quantal64/download-ubuntu +103 -0
- data/boxes/quantal64/lxc-template +567 -0
- data/boxes/quantal64/metadata.json +9 -0
- data/development/Vagrantfile.1.0 +35 -0
- data/development/Vagrantfile.1.1 +55 -0
- data/development/lxc-configs/lxc-dev-box +37 -0
- data/development/lxc-configs/vbox +37 -0
- data/development/shell-provisioning/upgrade-kernel +14 -0
- data/development/site.pp +125 -0
- data/example/Vagrantfile +42 -0
- data/example/puppet/manifests/site.pp +5 -0
- data/example/puppet/modules/hello_world/manifests/init.pp +3 -0
- data/lib/vagrant-lxc.rb +6 -0
- data/lib/vagrant-lxc/action.rb +188 -0
- data/lib/vagrant-lxc/action/base_action.rb +11 -0
- data/lib/vagrant-lxc/action/boot.rb +55 -0
- data/lib/vagrant-lxc/action/check_created.rb +17 -0
- data/lib/vagrant-lxc/action/check_running.rb +17 -0
- data/lib/vagrant-lxc/action/create.rb +14 -0
- data/lib/vagrant-lxc/action/created.rb +16 -0
- data/lib/vagrant-lxc/action/destroy.rb +14 -0
- data/lib/vagrant-lxc/action/forced_halt.rb +22 -0
- data/lib/vagrant-lxc/action/handle_box_metadata.rb +47 -0
- data/lib/vagrant-lxc/action/is_running.rb +15 -0
- data/lib/vagrant-lxc/action/network.rb +21 -0
- data/lib/vagrant-lxc/action/share_folders.rb +65 -0
- data/lib/vagrant-lxc/config.rb +14 -0
- data/lib/vagrant-lxc/container.rb +170 -0
- data/lib/vagrant-lxc/container/cli.rb +124 -0
- data/lib/vagrant-lxc/errors.rb +12 -0
- data/lib/vagrant-lxc/machine_state.rb +25 -0
- data/lib/vagrant-lxc/plugin.rb +23 -0
- data/lib/vagrant-lxc/provider.rb +74 -0
- data/lib/vagrant-lxc/version.rb +5 -0
- data/lib/vendored_vagrant.rb +9 -0
- data/locales/en.yml +17 -0
- data/spec/fixtures/sample-arp-output +4 -0
- data/spec/fixtures/sample-config +47 -0
- data/spec/spec_helper.rb +32 -0
- data/spec/support/unit_example_group.rb +28 -0
- data/spec/unit/action/handle_box_metadata_spec.rb +44 -0
- data/spec/unit/container/cli_spec.rb +148 -0
- data/spec/unit/container_spec.rb +151 -0
- data/spec/unit/machine_state_spec.rb +39 -0
- data/spec/unit_helper.rb +9 -0
- data/tasks/boxes.rake +17 -0
- data/tasks/spec.rake +30 -0
- data/vagrant-lxc.gemspec +32 -0
- data/vendor/.gitkeep +0 -0
- data/vendor/vagrant/.gitignore +31 -0
- data/vendor/vagrant/.travis.yml +7 -0
- data/vendor/vagrant/.yardopts +1 -0
- data/vendor/vagrant/CHANGELOG.md +803 -0
- data/vendor/vagrant/Gemfile +3 -0
- data/vendor/vagrant/LICENSE +21 -0
- data/vendor/vagrant/README.md +89 -0
- data/vendor/vagrant/Rakefile +18 -0
- data/vendor/vagrant/bin/vagrant +84 -0
- data/vendor/vagrant/config/default.rb +35 -0
- data/vendor/vagrant/contrib/README.md +12 -0
- data/vendor/vagrant/contrib/bash/completion.sh +3 -0
- data/vendor/vagrant/contrib/emacs/vagrant.el +8 -0
- data/vendor/vagrant/contrib/vim/vagrantfile.vim +9 -0
- data/vendor/vagrant/keys/README.md +17 -0
- data/vendor/vagrant/keys/vagrant +27 -0
- data/vendor/vagrant/keys/vagrant.pub +1 -0
- data/vendor/vagrant/lib/vagrant.rb +251 -0
- data/vendor/vagrant/lib/vagrant/action.rb +42 -0
- data/vendor/vagrant/lib/vagrant/action/builder.rb +154 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/box_add.rb +79 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/call.rb +67 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/config_validate.rb +30 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/confirm.rb +38 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/env_set.rb +24 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/graceful_halt.rb +73 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/handle_box_url.rb +43 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb +117 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/lock.rb +57 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/nfs.rb +117 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/provision.rb +70 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/set_hostname.rb +27 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/ssh_exec.rb +42 -0
- data/vendor/vagrant/lib/vagrant/action/builtin/ssh_run.rb +43 -0
- data/vendor/vagrant/lib/vagrant/action/general/package.rb +102 -0
- data/vendor/vagrant/lib/vagrant/action/hook.rb +103 -0
- data/vendor/vagrant/lib/vagrant/action/runner.rb +69 -0
- data/vendor/vagrant/lib/vagrant/action/warden.rb +103 -0
- data/vendor/vagrant/lib/vagrant/box.rb +93 -0
- data/vendor/vagrant/lib/vagrant/box_collection.rb +315 -0
- data/vendor/vagrant/lib/vagrant/cli.rb +82 -0
- data/vendor/vagrant/lib/vagrant/config.rb +63 -0
- data/vendor/vagrant/lib/vagrant/config/container.rb +37 -0
- data/vendor/vagrant/lib/vagrant/config/loader.rb +222 -0
- data/vendor/vagrant/lib/vagrant/config/v1.rb +9 -0
- data/vendor/vagrant/lib/vagrant/config/v1/dummy_config.rb +13 -0
- data/vendor/vagrant/lib/vagrant/config/v1/loader.rb +105 -0
- data/vendor/vagrant/lib/vagrant/config/v1/root.rb +60 -0
- data/vendor/vagrant/lib/vagrant/config/v2.rb +9 -0
- data/vendor/vagrant/lib/vagrant/config/v2/dummy_config.rb +13 -0
- data/vendor/vagrant/lib/vagrant/config/v2/loader.rb +141 -0
- data/vendor/vagrant/lib/vagrant/config/v2/root.rb +105 -0
- data/vendor/vagrant/lib/vagrant/config/v2/util.rb +21 -0
- data/vendor/vagrant/lib/vagrant/config/version_base.rb +80 -0
- data/vendor/vagrant/lib/vagrant/downloaders.rb +7 -0
- data/vendor/vagrant/lib/vagrant/downloaders/base.rb +22 -0
- data/vendor/vagrant/lib/vagrant/downloaders/file.rb +28 -0
- data/vendor/vagrant/lib/vagrant/downloaders/http.rb +116 -0
- data/vendor/vagrant/lib/vagrant/environment.rb +729 -0
- data/vendor/vagrant/lib/vagrant/errors.rb +486 -0
- data/vendor/vagrant/lib/vagrant/hosts.rb +28 -0
- data/vendor/vagrant/lib/vagrant/machine.rb +325 -0
- data/vendor/vagrant/lib/vagrant/machine_state.rb +45 -0
- data/vendor/vagrant/lib/vagrant/plugin.rb +6 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1.rb +19 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/command.rb +169 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/communicator.rb +98 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/config.rb +112 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/errors.rb +15 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/guest.rb +92 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/host.rb +66 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/manager.rb +131 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/plugin.rb +229 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/provider.rb +68 -0
- data/vendor/vagrant/lib/vagrant/plugin/v1/provisioner.rb +50 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2.rb +22 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/command.rb +234 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/communicator.rb +98 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/components.rb +29 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/config.rb +101 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/errors.rb +15 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/guest.rb +92 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/host.rb +66 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/manager.rb +158 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/plugin.rb +217 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/provider.rb +69 -0
- data/vendor/vagrant/lib/vagrant/plugin/v2/provisioner.rb +47 -0
- data/vendor/vagrant/lib/vagrant/registry.rb +78 -0
- data/vendor/vagrant/lib/vagrant/ssh.rb +132 -0
- data/vendor/vagrant/lib/vagrant/test_helpers.rb +154 -0
- data/vendor/vagrant/lib/vagrant/ui.rb +170 -0
- data/vendor/vagrant/lib/vagrant/util.rb +12 -0
- data/vendor/vagrant/lib/vagrant/util/ansi_escape_code_remover.rb +34 -0
- data/vendor/vagrant/lib/vagrant/util/busy.rb +59 -0
- data/vendor/vagrant/lib/vagrant/util/counter.rb +24 -0
- data/vendor/vagrant/lib/vagrant/util/file_checksum.rb +38 -0
- data/vendor/vagrant/lib/vagrant/util/file_mode.rb +12 -0
- data/vendor/vagrant/lib/vagrant/util/hash_with_indifferent_access.rb +63 -0
- data/vendor/vagrant/lib/vagrant/util/is_port_open.rb +38 -0
- data/vendor/vagrant/lib/vagrant/util/line_ending_helpers.rb +14 -0
- data/vendor/vagrant/lib/vagrant/util/network_ip.rb +28 -0
- data/vendor/vagrant/lib/vagrant/util/platform.rb +68 -0
- data/vendor/vagrant/lib/vagrant/util/retryable.rb +31 -0
- data/vendor/vagrant/lib/vagrant/util/safe_exec.rb +36 -0
- data/vendor/vagrant/lib/vagrant/util/safe_puts.rb +31 -0
- data/vendor/vagrant/lib/vagrant/util/scoped_hash_override.rb +45 -0
- data/vendor/vagrant/lib/vagrant/util/ssh.rb +126 -0
- data/vendor/vagrant/lib/vagrant/util/stacked_proc_runner.rb +35 -0
- data/vendor/vagrant/lib/vagrant/util/string_block_editor.rb +75 -0
- data/vendor/vagrant/lib/vagrant/util/subprocess.rb +270 -0
- data/vendor/vagrant/lib/vagrant/util/template_renderer.rb +83 -0
- data/vendor/vagrant/lib/vagrant/util/which.rb +43 -0
- data/vendor/vagrant/lib/vagrant/version.rb +6 -0
- data/vendor/vagrant/plugins/README.md +5 -0
- data/vendor/vagrant/plugins/commands/box/command/add.rb +52 -0
- data/vendor/vagrant/plugins/commands/box/command/list.rb +41 -0
- data/vendor/vagrant/plugins/commands/box/command/remove.rb +37 -0
- data/vendor/vagrant/plugins/commands/box/command/repackage.rb +43 -0
- data/vendor/vagrant/plugins/commands/box/command/root.rb +75 -0
- data/vendor/vagrant/plugins/commands/box/plugin.rb +15 -0
- data/vendor/vagrant/plugins/commands/destroy/command.rb +31 -0
- data/vendor/vagrant/plugins/commands/destroy/plugin.rb +18 -0
- data/vendor/vagrant/plugins/commands/halt/command.rb +33 -0
- data/vendor/vagrant/plugins/commands/halt/plugin.rb +18 -0
- data/vendor/vagrant/plugins/commands/init/command.rb +40 -0
- data/vendor/vagrant/plugins/commands/init/plugin.rb +18 -0
- data/vendor/vagrant/plugins/commands/package/command.rb +78 -0
- data/vendor/vagrant/plugins/commands/package/plugin.rb +18 -0
- data/vendor/vagrant/plugins/commands/plugin/action.rb +52 -0
- data/vendor/vagrant/plugins/commands/plugin/action/bundler_check.rb +25 -0
- data/vendor/vagrant/plugins/commands/plugin/action/install_gem.rb +70 -0
- data/vendor/vagrant/plugins/commands/plugin/action/license_plugin.rb +54 -0
- data/vendor/vagrant/plugins/commands/plugin/action/list_plugins.rb +54 -0
- data/vendor/vagrant/plugins/commands/plugin/action/prune_gems.rb +149 -0
- data/vendor/vagrant/plugins/commands/plugin/action/uninstall_plugin.rb +23 -0
- data/vendor/vagrant/plugins/commands/plugin/command/base.rb +22 -0
- data/vendor/vagrant/plugins/commands/plugin/command/install.rb +39 -0
- data/vendor/vagrant/plugins/commands/plugin/command/license.rb +31 -0
- data/vendor/vagrant/plugins/commands/plugin/command/list.rb +28 -0
- data/vendor/vagrant/plugins/commands/plugin/command/root.rb +75 -0
- data/vendor/vagrant/plugins/commands/plugin/command/uninstall.rb +28 -0
- data/vendor/vagrant/plugins/commands/plugin/gem_helper.rb +74 -0
- data/vendor/vagrant/plugins/commands/plugin/plugin.rb +22 -0
- data/vendor/vagrant/plugins/commands/plugin/state_file.rb +57 -0
- data/vendor/vagrant/plugins/commands/provision/command.rb +34 -0
- data/vendor/vagrant/plugins/commands/provision/plugin.rb +18 -0
- data/vendor/vagrant/plugins/commands/reload/command.rb +37 -0
- data/vendor/vagrant/plugins/commands/reload/plugin.rb +18 -0
- data/vendor/vagrant/plugins/commands/resume/command.rb +25 -0
- data/vendor/vagrant/plugins/commands/resume/plugin.rb +17 -0
- data/vendor/vagrant/plugins/commands/ssh/command.rb +66 -0
- data/vendor/vagrant/plugins/commands/ssh/plugin.rb +17 -0
- data/vendor/vagrant/plugins/commands/ssh_config/command.rb +49 -0
- data/vendor/vagrant/plugins/commands/ssh_config/plugin.rb +18 -0
- data/vendor/vagrant/plugins/commands/status/command.rb +39 -0
- data/vendor/vagrant/plugins/commands/status/plugin.rb +18 -0
- data/vendor/vagrant/plugins/commands/suspend/command.rb +25 -0
- data/vendor/vagrant/plugins/commands/suspend/plugin.rb +18 -0
- data/vendor/vagrant/plugins/commands/up/command.rb +45 -0
- data/vendor/vagrant/plugins/commands/up/plugin.rb +17 -0
- data/vendor/vagrant/plugins/commands/up/start_mixins.rb +26 -0
- data/vendor/vagrant/plugins/communicators/ssh/communicator.rb +317 -0
- data/vendor/vagrant/plugins/communicators/ssh/plugin.rb +19 -0
- data/vendor/vagrant/plugins/guests/arch/guest.rb +41 -0
- data/vendor/vagrant/plugins/guests/arch/plugin.rb +15 -0
- data/vendor/vagrant/plugins/guests/debian/guest.rb +72 -0
- data/vendor/vagrant/plugins/guests/debian/plugin.rb +15 -0
- data/vendor/vagrant/plugins/guests/fedora/guest.rb +71 -0
- data/vendor/vagrant/plugins/guests/fedora/plugin.rb +15 -0
- data/vendor/vagrant/plugins/guests/freebsd/config.rb +13 -0
- data/vendor/vagrant/plugins/guests/freebsd/guest.rb +70 -0
- data/vendor/vagrant/plugins/guests/freebsd/plugin.rb +20 -0
- data/vendor/vagrant/plugins/guests/gentoo/guest.rb +51 -0
- data/vendor/vagrant/plugins/guests/gentoo/plugin.rb +15 -0
- data/vendor/vagrant/plugins/guests/linux/config.rb +13 -0
- data/vendor/vagrant/plugins/guests/linux/guest.rb +118 -0
- data/vendor/vagrant/plugins/guests/linux/plugin.rb +20 -0
- data/vendor/vagrant/plugins/guests/openbsd/guest.rb +13 -0
- data/vendor/vagrant/plugins/guests/openbsd/plugin.rb +15 -0
- data/vendor/vagrant/plugins/guests/redhat/guest.rb +74 -0
- data/vendor/vagrant/plugins/guests/redhat/plugin.rb +15 -0
- data/vendor/vagrant/plugins/guests/solaris/config.rb +18 -0
- data/vendor/vagrant/plugins/guests/solaris/guest.rb +73 -0
- data/vendor/vagrant/plugins/guests/solaris/plugin.rb +20 -0
- data/vendor/vagrant/plugins/guests/suse/guest.rb +24 -0
- data/vendor/vagrant/plugins/guests/suse/plugin.rb +15 -0
- data/vendor/vagrant/plugins/guests/ubuntu/guest.rb +44 -0
- data/vendor/vagrant/plugins/guests/ubuntu/plugin.rb +15 -0
- data/vendor/vagrant/plugins/hosts/arch/host.rb +68 -0
- data/vendor/vagrant/plugins/hosts/arch/plugin.rb +15 -0
- data/vendor/vagrant/plugins/hosts/bsd/host.rb +102 -0
- data/vendor/vagrant/plugins/hosts/bsd/plugin.rb +15 -0
- data/vendor/vagrant/plugins/hosts/fedora/host.rb +51 -0
- data/vendor/vagrant/plugins/hosts/fedora/plugin.rb +15 -0
- data/vendor/vagrant/plugins/hosts/freebsd/host.rb +43 -0
- data/vendor/vagrant/plugins/hosts/freebsd/plugin.rb +15 -0
- data/vendor/vagrant/plugins/hosts/gentoo/host.rb +24 -0
- data/vendor/vagrant/plugins/hosts/gentoo/plugin.rb +15 -0
- data/vendor/vagrant/plugins/hosts/linux/host.rb +95 -0
- data/vendor/vagrant/plugins/hosts/linux/plugin.rb +15 -0
- data/vendor/vagrant/plugins/hosts/opensuse/host.rb +34 -0
- data/vendor/vagrant/plugins/hosts/opensuse/plugin.rb +15 -0
- data/vendor/vagrant/plugins/hosts/windows/host.rb +17 -0
- data/vendor/vagrant/plugins/hosts/windows/plugin.rb +15 -0
- data/vendor/vagrant/plugins/kernel_v1/config/nfs.rb +20 -0
- data/vendor/vagrant/plugins/kernel_v1/config/package.rb +17 -0
- data/vendor/vagrant/plugins/kernel_v1/config/ssh.rb +46 -0
- data/vendor/vagrant/plugins/kernel_v1/config/vagrant.rb +31 -0
- data/vendor/vagrant/plugins/kernel_v1/config/vm.rb +184 -0
- data/vendor/vagrant/plugins/kernel_v1/plugin.rb +44 -0
- data/vendor/vagrant/plugins/kernel_v2/config/nfs.rb +10 -0
- data/vendor/vagrant/plugins/kernel_v2/config/package.rb +9 -0
- data/vendor/vagrant/plugins/kernel_v2/config/ssh.rb +35 -0
- data/vendor/vagrant/plugins/kernel_v2/config/vagrant.rb +9 -0
- data/vendor/vagrant/plugins/kernel_v2/config/vm.rb +314 -0
- data/vendor/vagrant/plugins/kernel_v2/config/vm_provisioner.rb +40 -0
- data/vendor/vagrant/plugins/kernel_v2/config/vm_subvm.rb +30 -0
- data/vendor/vagrant/plugins/kernel_v2/plugin.rb +44 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action.rb +308 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/boot.rb +49 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/check_accessible.rb +23 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/check_created.rb +21 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/check_guest_additions.rb +45 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/check_running.rb +21 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/check_virtualbox.rb +22 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/clean_machine_folder.rb +43 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/clear_forwarded_ports.rb +18 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/clear_network_interfaces.rb +31 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/clear_shared_folders.rb +17 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/created.rb +20 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/customize.rb +36 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/destroy.rb +19 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/destroy_confirm.rb +17 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/destroy_unused_network_interfaces.rb +16 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/discard_state.rb +20 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/export.rb +57 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/forced_halt.rb +25 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/forward_ports.rb +79 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/import.rb +51 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/is_paused.rb +20 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/is_running.rb +20 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/is_saved.rb +20 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/match_mac_address.rb +21 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/message_not_created.rb +16 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/message_not_running.rb +16 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/message_will_not_destroy.rb +17 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/network.rb +366 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/package.rb +20 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/package_vagrantfile.rb +33 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb +35 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/prepare_nfs_settings.rb +51 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/prune_nfs_exports.rb +20 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/resume.rb +25 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/sane_defaults.rb +87 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/set_name.rb +40 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/setup_package_files.rb +51 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/share_folders.rb +113 -0
- data/vendor/vagrant/plugins/providers/virtualbox/action/suspend.rb +20 -0
- data/vendor/vagrant/plugins/providers/virtualbox/config.rb +82 -0
- data/vendor/vagrant/plugins/providers/virtualbox/driver/base.rb +344 -0
- data/vendor/vagrant/plugins/providers/virtualbox/driver/meta.rb +141 -0
- data/vendor/vagrant/plugins/providers/virtualbox/driver/version_4_0.rb +481 -0
- data/vendor/vagrant/plugins/providers/virtualbox/driver/version_4_1.rb +481 -0
- data/vendor/vagrant/plugins/providers/virtualbox/driver/version_4_2.rb +471 -0
- data/vendor/vagrant/plugins/providers/virtualbox/model/forwarded_port.rb +58 -0
- data/vendor/vagrant/plugins/providers/virtualbox/plugin.rb +42 -0
- data/vendor/vagrant/plugins/providers/virtualbox/provider.rb +92 -0
- data/vendor/vagrant/plugins/providers/virtualbox/util/compile_forwarded_ports.rb +31 -0
- data/vendor/vagrant/plugins/provisioners/chef/config/base.rb +65 -0
- data/vendor/vagrant/plugins/provisioners/chef/config/chef_client.rb +39 -0
- data/vendor/vagrant/plugins/provisioners/chef/config/chef_solo.rb +87 -0
- data/vendor/vagrant/plugins/provisioners/chef/plugin.rb +33 -0
- data/vendor/vagrant/plugins/provisioners/chef/provisioner/base.rb +91 -0
- data/vendor/vagrant/plugins/provisioners/chef/provisioner/chef_client.rb +103 -0
- data/vendor/vagrant/plugins/provisioners/chef/provisioner/chef_solo.rb +182 -0
- data/vendor/vagrant/plugins/provisioners/puppet/config/puppet.rb +70 -0
- data/vendor/vagrant/plugins/provisioners/puppet/config/puppet_server.rb +16 -0
- data/vendor/vagrant/plugins/provisioners/puppet/plugin.rb +33 -0
- data/vendor/vagrant/plugins/provisioners/puppet/provisioner/puppet.rb +110 -0
- data/vendor/vagrant/plugins/provisioners/puppet/provisioner/puppet_server.rb +67 -0
- data/vendor/vagrant/plugins/provisioners/shell/config.rb +46 -0
- data/vendor/vagrant/plugins/provisioners/shell/plugin.rb +23 -0
- data/vendor/vagrant/plugins/provisioners/shell/provisioner.rb +66 -0
- data/vendor/vagrant/tasks/acceptance.rake +113 -0
- data/vendor/vagrant/tasks/bundler.rake +3 -0
- data/vendor/vagrant/tasks/test.rake +20 -0
- data/vendor/vagrant/templates/commands/init/Vagrantfile.erb +111 -0
- data/vendor/vagrant/templates/commands/ssh_config/config.erb +16 -0
- data/vendor/vagrant/templates/config/messages.erb +14 -0
- data/vendor/vagrant/templates/config/validation_failed.erb +7 -0
- data/vendor/vagrant/templates/guests/arch/network_dhcp.erb +4 -0
- data/vendor/vagrant/templates/guests/arch/network_static.erb +6 -0
- data/vendor/vagrant/templates/guests/debian/network_dhcp.erb +11 -0
- data/vendor/vagrant/templates/guests/debian/network_static.erb +7 -0
- data/vendor/vagrant/templates/guests/fedora/network_dhcp.erb +6 -0
- data/vendor/vagrant/templates/guests/fedora/network_static.erb +13 -0
- data/vendor/vagrant/templates/guests/freebsd/network_dhcp.erb +3 -0
- data/vendor/vagrant/templates/guests/freebsd/network_static.erb +3 -0
- data/vendor/vagrant/templates/guests/gentoo/network_dhcp.erb +4 -0
- data/vendor/vagrant/templates/guests/gentoo/network_static.erb +4 -0
- data/vendor/vagrant/templates/guests/redhat/network_dhcp.erb +6 -0
- data/vendor/vagrant/templates/guests/redhat/network_static.erb +7 -0
- data/vendor/vagrant/templates/locales/en.yml +993 -0
- data/vendor/vagrant/templates/nfs/exports.erb +5 -0
- data/vendor/vagrant/templates/nfs/exports_freebsd.erb +5 -0
- data/vendor/vagrant/templates/nfs/exports_linux.erb +5 -0
- data/vendor/vagrant/templates/package_Vagrantfile.erb +11 -0
- data/vendor/vagrant/templates/provisioners/chef_client/client.erb +32 -0
- data/vendor/vagrant/templates/provisioners/chef_solo/solo.erb +25 -0
- data/vendor/vagrant/templates/rgloader.rb +9 -0
- data/vendor/vagrant/test/acceptance/base.rb +48 -0
- data/vendor/vagrant/test/acceptance/box_test.rb +99 -0
- data/vendor/vagrant/test/acceptance/destroy_test.rb +37 -0
- data/vendor/vagrant/test/acceptance/halt_test.rb +72 -0
- data/vendor/vagrant/test/acceptance/init_test.rb +33 -0
- data/vendor/vagrant/test/acceptance/networking/host_only_test.rb +37 -0
- data/vendor/vagrant/test/acceptance/networking/port_forward_test.rb +125 -0
- data/vendor/vagrant/test/acceptance/package_test.rb +46 -0
- data/vendor/vagrant/test/acceptance/provisioning/basic_test.rb +61 -0
- data/vendor/vagrant/test/acceptance/provisioning/chef_solo_test.rb +37 -0
- data/vendor/vagrant/test/acceptance/provisioning/shell_test.rb +53 -0
- data/vendor/vagrant/test/acceptance/resume_test.rb +17 -0
- data/vendor/vagrant/test/acceptance/shared_folders_test.rb +84 -0
- data/vendor/vagrant/test/acceptance/skeletons/chef_solo_basic/README.md +3 -0
- data/vendor/vagrant/test/acceptance/skeletons/chef_solo_basic/cookbooks/basic/recipes/default.rb +5 -0
- data/vendor/vagrant/test/acceptance/skeletons/chef_solo_json/README.md +3 -0
- data/vendor/vagrant/test/acceptance/skeletons/chef_solo_json/cookbooks/basic/recipes/default.rb +6 -0
- data/vendor/vagrant/test/acceptance/skeletons/provisioner_multi/README.md +3 -0
- data/vendor/vagrant/test/acceptance/skeletons/provisioner_multi/cookbooks/basic/recipes/default.rb +5 -0
- data/vendor/vagrant/test/acceptance/ssh_test.rb +46 -0
- data/vendor/vagrant/test/acceptance/support/config.rb +42 -0
- data/vendor/vagrant/test/acceptance/support/isolated_environment.rb +118 -0
- data/vendor/vagrant/test/acceptance/support/matchers/have_color.rb +9 -0
- data/vendor/vagrant/test/acceptance/support/matchers/match_output.rb +14 -0
- data/vendor/vagrant/test/acceptance/support/matchers/succeed.rb +14 -0
- data/vendor/vagrant/test/acceptance/support/network_tests.rb +29 -0
- data/vendor/vagrant/test/acceptance/support/output.rb +95 -0
- data/vendor/vagrant/test/acceptance/support/shared/base_context.rb +72 -0
- data/vendor/vagrant/test/acceptance/support/shared/command_examples.rb +33 -0
- data/vendor/vagrant/test/acceptance/support/virtualbox.rb +36 -0
- data/vendor/vagrant/test/acceptance/suspend_test.rb +56 -0
- data/vendor/vagrant/test/acceptance/up_basic_test.rb +33 -0
- data/vendor/vagrant/test/acceptance/up_with_box_url.rb +40 -0
- data/vendor/vagrant/test/acceptance/vagrant_test.rb +47 -0
- data/vendor/vagrant/test/acceptance/version_test.rb +15 -0
- data/vendor/vagrant/test/config/acceptance_boxes.yml +7 -0
- data/vendor/vagrant/test/support/isolated_environment.rb +46 -0
- data/vendor/vagrant/test/support/tempdir.rb +43 -0
- data/vendor/vagrant/test/unit/base.rb +27 -0
- data/vendor/vagrant/test/unit/support/dummy_provider.rb +16 -0
- data/vendor/vagrant/test/unit/support/isolated_environment.rb +177 -0
- data/vendor/vagrant/test/unit/support/shared/base_context.rb +104 -0
- data/vendor/vagrant/test/unit/vagrant/action/builder_test.rb +196 -0
- data/vendor/vagrant/test/unit/vagrant/action/builtin/call_test.rb +145 -0
- data/vendor/vagrant/test/unit/vagrant/action/builtin/confirm_test.rb +36 -0
- data/vendor/vagrant/test/unit/vagrant/action/builtin/env_set_test.rb +20 -0
- data/vendor/vagrant/test/unit/vagrant/action/builtin/graceful_halt_test.rb +61 -0
- data/vendor/vagrant/test/unit/vagrant/action/builtin/lock_test.rb +98 -0
- data/vendor/vagrant/test/unit/vagrant/action/builtin/ssh_exec_test.rb +57 -0
- data/vendor/vagrant/test/unit/vagrant/action/hook_test.rb +101 -0
- data/vendor/vagrant/test/unit/vagrant/action/runner_test.rb +71 -0
- data/vendor/vagrant/test/unit/vagrant/action/warden_test.rb +92 -0
- data/vendor/vagrant/test/unit/vagrant/box_collection_test.rb +224 -0
- data/vendor/vagrant/test/unit/vagrant/box_test.rb +109 -0
- data/vendor/vagrant/test/unit/vagrant/cli_test.rb +27 -0
- data/vendor/vagrant/test/unit/vagrant/config/loader_test.rb +184 -0
- data/vendor/vagrant/test/unit/vagrant/config/v1/dummy_config_test.rb +24 -0
- data/vendor/vagrant/test/unit/vagrant/config/v1/loader_test.rb +145 -0
- data/vendor/vagrant/test/unit/vagrant/config/v1/root_test.rb +40 -0
- data/vendor/vagrant/test/unit/vagrant/config/v2/dummy_config_test.rb +24 -0
- data/vendor/vagrant/test/unit/vagrant/config/v2/loader_test.rb +151 -0
- data/vendor/vagrant/test/unit/vagrant/config/v2/root_test.rb +97 -0
- data/vendor/vagrant/test/unit/vagrant/config/v2/util_test.rb +21 -0
- data/vendor/vagrant/test/unit/vagrant/config_test.rb +66 -0
- data/vendor/vagrant/test/unit/vagrant/downloaders/base_test.rb +14 -0
- data/vendor/vagrant/test/unit/vagrant/downloaders/file_test.rb +87 -0
- data/vendor/vagrant/test/unit/vagrant/downloaders/http_test.rb +23 -0
- data/vendor/vagrant/test/unit/vagrant/environment_test.rb +571 -0
- data/vendor/vagrant/test/unit/vagrant/hosts_test.rb +37 -0
- data/vendor/vagrant/test/unit/vagrant/machine_state_test.rb +26 -0
- data/vendor/vagrant/test/unit/vagrant/machine_test.rb +418 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v1/command_test.rb +143 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v1/communicator_test.rb +9 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v1/config_test.rb +50 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v1/host_test.rb +5 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v1/manager_test.rb +114 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v1/plugin_test.rb +267 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v1/provider_test.rb +18 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v2/command_test.rb +238 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v2/communicator_test.rb +9 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v2/components_test.rb +17 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v2/config_test.rb +60 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v2/host_test.rb +5 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v2/manager_test.rb +157 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v2/plugin_test.rb +287 -0
- data/vendor/vagrant/test/unit/vagrant/plugin/v2/provider_test.rb +18 -0
- data/vendor/vagrant/test/unit/vagrant/registry_test.rb +128 -0
- data/vendor/vagrant/test/unit/vagrant/util/ansi_escape_code_remover_test.rb +16 -0
- data/vendor/vagrant/test/unit/vagrant/util/file_checksum_test.rb +23 -0
- data/vendor/vagrant/test/unit/vagrant/util/hash_with_indifferent_access_test.rb +38 -0
- data/vendor/vagrant/test/unit/vagrant/util/is_port_open_test.rb +53 -0
- data/vendor/vagrant/test/unit/vagrant/util/line_endings_helper_test.rb +16 -0
- data/vendor/vagrant/test/unit/vagrant/util/network_ip_test.rb +17 -0
- data/vendor/vagrant/test/unit/vagrant/util/retryable_test.rb +106 -0
- data/vendor/vagrant/test/unit/vagrant/util/scoped_hash_override_test.rb +48 -0
- data/vendor/vagrant/test/unit/vagrant/util/ssh_test.rb +30 -0
- data/vendor/vagrant/test/unit/vagrant/util/string_block_editor_test.rb +98 -0
- data/vendor/vagrant/test/unit/vagrant/util/which_test.rb +43 -0
- data/vendor/vagrant/test/unit/vagrant_test.rb +56 -0
- data/vendor/vagrant/vagrant.gemspec +69 -0
- metadata +642 -0
@@ -0,0 +1,20 @@
|
|
1
|
+
require 'rake/testtask'
|
2
|
+
require 'rspec/core/rake_task'
|
3
|
+
|
4
|
+
namespace :test do
|
5
|
+
RSpec::Core::RakeTask.new do |t|
|
6
|
+
t.name = "unit"
|
7
|
+
t.pattern = "test/unit/**/*_test.rb"
|
8
|
+
end
|
9
|
+
|
10
|
+
Rake::TestTask.new do |t|
|
11
|
+
t.name = "unit_old"
|
12
|
+
t.libs << "test/unit_legacy"
|
13
|
+
t.pattern = "test/unit_legacy/**/*_test.rb"
|
14
|
+
end
|
15
|
+
|
16
|
+
RSpec::Core::RakeTask.new do |t|
|
17
|
+
t.name = "acceptance"
|
18
|
+
t.pattern = "test/acceptance/**/*_test.rb"
|
19
|
+
end
|
20
|
+
end
|
@@ -0,0 +1,111 @@
|
|
1
|
+
# -*- mode: ruby -*-
|
2
|
+
# vi: set ft=ruby :
|
3
|
+
|
4
|
+
Vagrant.configure("2") do |config|
|
5
|
+
# All Vagrant configuration is done here. The most common configuration
|
6
|
+
# options are documented and commented below. For a complete reference,
|
7
|
+
# please see the online documentation at vagrantup.com.
|
8
|
+
|
9
|
+
# Every Vagrant virtual environment requires a box to build off of.
|
10
|
+
config.vm.box = "<%= box_name %>"
|
11
|
+
|
12
|
+
# The url from where the 'config.vm.box' box will be fetched if it
|
13
|
+
# doesn't already exist on the user's system.
|
14
|
+
<% if box_url.nil? %># <% end %>config.vm.box_url = "<%= box_url || "http://domain.com/path/to/above.box" %>"
|
15
|
+
|
16
|
+
# Create a forwarded port mapping which allows access to a specific port
|
17
|
+
# within the machine from a port on the host machine. In the example below,
|
18
|
+
# accessing "localhost:8080" will access port 80 on the guest machine.
|
19
|
+
# config.vm.network :forwarded_port, guest: 80, host: 8080
|
20
|
+
|
21
|
+
# Create a private network, which allows host-only access to the machine
|
22
|
+
# using a specific IP.
|
23
|
+
# config.vm.network :private_network, ip: "192.168.33.10"
|
24
|
+
|
25
|
+
# Create a public network, which generally matched to bridged network.
|
26
|
+
# Bridged networks make the machine appear as another physical device on
|
27
|
+
# your network.
|
28
|
+
# config.vm.network :public_network
|
29
|
+
|
30
|
+
# Share an additional folder to the guest VM. The first argument is
|
31
|
+
# the path on the host to the actual folder. The second argument is
|
32
|
+
# the path on the guest to mount the folder. And the optional third
|
33
|
+
# argument is a set of non-required options.
|
34
|
+
# config.vm.synced_folder "../data", "/vagrant_data"
|
35
|
+
|
36
|
+
# Provider-specific configuration so you can fine-tune various
|
37
|
+
# backing providers for Vagrant. These expose provider-specific options.
|
38
|
+
# Example for VirtualBox:
|
39
|
+
#
|
40
|
+
# config.vm.provider :virtualbox do |vb|
|
41
|
+
# # Don't boot with headless mode
|
42
|
+
# vb.gui = true
|
43
|
+
#
|
44
|
+
# # Use VBoxManage to customize the VM. For example to change memory:
|
45
|
+
# vb.customize ["modifyvm", :id, "--memory", "1024"]
|
46
|
+
# end
|
47
|
+
#
|
48
|
+
# View the documentation for the provider you're using for more
|
49
|
+
# information on available options.
|
50
|
+
|
51
|
+
# Enable provisioning with Puppet stand alone. Puppet manifests
|
52
|
+
# are contained in a directory path relative to this Vagrantfile.
|
53
|
+
# You will need to create the manifests directory and a manifest in
|
54
|
+
# the file <%= box_name %>.pp in the manifests_path directory.
|
55
|
+
#
|
56
|
+
# An example Puppet manifest to provision the message of the day:
|
57
|
+
#
|
58
|
+
# # group { "puppet":
|
59
|
+
# # ensure => "present",
|
60
|
+
# # }
|
61
|
+
# #
|
62
|
+
# # File { owner => 0, group => 0, mode => 0644 }
|
63
|
+
# #
|
64
|
+
# # file { '/etc/motd':
|
65
|
+
# # content => "Welcome to your Vagrant-built virtual machine!
|
66
|
+
# # Managed by Puppet.\n"
|
67
|
+
# # }
|
68
|
+
#
|
69
|
+
# config.vm.provision :puppet do |puppet|
|
70
|
+
# puppet.manifests_path = "manifests"
|
71
|
+
# puppet.manifest_file = "<%= box_name %>.pp"
|
72
|
+
# end
|
73
|
+
|
74
|
+
# Enable provisioning with chef solo, specifying a cookbooks path, roles
|
75
|
+
# path, and data_bags path (all relative to this Vagrantfile), and adding
|
76
|
+
# some recipes and/or roles.
|
77
|
+
#
|
78
|
+
# config.vm.provision :chef_solo do |chef|
|
79
|
+
# chef.cookbooks_path = "../my-recipes/cookbooks"
|
80
|
+
# chef.roles_path = "../my-recipes/roles"
|
81
|
+
# chef.data_bags_path = "../my-recipes/data_bags"
|
82
|
+
# chef.add_recipe "mysql"
|
83
|
+
# chef.add_role "web"
|
84
|
+
#
|
85
|
+
# # You may also specify custom JSON attributes:
|
86
|
+
# chef.json = { :mysql_password => "foo" }
|
87
|
+
# end
|
88
|
+
|
89
|
+
# Enable provisioning with chef server, specifying the chef server URL,
|
90
|
+
# and the path to the validation key (relative to this Vagrantfile).
|
91
|
+
#
|
92
|
+
# The Opscode Platform uses HTTPS. Substitute your organization for
|
93
|
+
# ORGNAME in the URL and validation key.
|
94
|
+
#
|
95
|
+
# If you have your own Chef Server, use the appropriate URL, which may be
|
96
|
+
# HTTP instead of HTTPS depending on your configuration. Also change the
|
97
|
+
# validation key to validation.pem.
|
98
|
+
#
|
99
|
+
# config.vm.provision :chef_client do |chef|
|
100
|
+
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
|
101
|
+
# chef.validation_key_path = "ORGNAME-validator.pem"
|
102
|
+
# end
|
103
|
+
#
|
104
|
+
# If you're using the Opscode platform, your validator client is
|
105
|
+
# ORGNAME-validator, replacing ORGNAME with your organization name.
|
106
|
+
#
|
107
|
+
# If you have your own Chef Server, the default validation client name is
|
108
|
+
# chef-validator, unless you changed the configuration.
|
109
|
+
#
|
110
|
+
# chef.validation_client_name = "ORGNAME-validator"
|
111
|
+
end
|
@@ -0,0 +1,16 @@
|
|
1
|
+
Host <%= host_key %>
|
2
|
+
HostName <%= ssh_host %>
|
3
|
+
User <%= ssh_user %>
|
4
|
+
Port <%= ssh_port %>
|
5
|
+
UserKnownHostsFile /dev/null
|
6
|
+
StrictHostKeyChecking no
|
7
|
+
PasswordAuthentication no
|
8
|
+
IdentityFile "<%= private_key_path %>"
|
9
|
+
IdentitiesOnly yes
|
10
|
+
LogLevel FATAL
|
11
|
+
<% if forward_agent -%>
|
12
|
+
ForwardAgent yes
|
13
|
+
<% end -%>
|
14
|
+
<% if forward_x11 -%>
|
15
|
+
ForwardX11 yes
|
16
|
+
<% end -%>
|
@@ -0,0 +1,11 @@
|
|
1
|
+
#VAGRANT-BEGIN
|
2
|
+
# The contents below are automatically generated by Vagrant. Do not modify.
|
3
|
+
auto eth<%= options[:interface] %>
|
4
|
+
iface eth<%= options[:interface] %> inet dhcp
|
5
|
+
<% if !options[:use_dhcp_assigned_default_route] %>
|
6
|
+
post-up route del default dev $IFACE
|
7
|
+
<% else %>
|
8
|
+
# needed as some newer distribution do not properly load routes, ubuntu 12.04
|
9
|
+
post-up dhclient $IFACE
|
10
|
+
<% end %>
|
11
|
+
#VAGRANT-END
|
@@ -0,0 +1,13 @@
|
|
1
|
+
#VAGRANT-BEGIN
|
2
|
+
# The contents below are automatically generated by Vagrant. Do not modify.
|
3
|
+
NM_CONTROLLED=no
|
4
|
+
BOOTPROTO=static
|
5
|
+
ONBOOT=yes
|
6
|
+
IPADDR=<%= options[:ip] %>
|
7
|
+
NETMASK=<%= options[:netmask] %>
|
8
|
+
DEVICE=p7p<%= options[:interface] %>
|
9
|
+
<%= options[:gateway] ? "GATEWAY=#{options[:gateway]}" : '' %>
|
10
|
+
<%= options[:mac_address] ? "HWADDR=#{options[:mac_address]}" : '' %>
|
11
|
+
<%= options[:dns1] ? "DNS1=#{options[:dns1]}" : 'DNS1=8.8.4.4' %>
|
12
|
+
<%= options[:dns2] ? "DNS2=#{options[:dns2]}" : 'DNS1=8.8.8.8' %>
|
13
|
+
#VAGRANT-END
|
@@ -0,0 +1,993 @@
|
|
1
|
+
en:
|
2
|
+
vagrant:
|
3
|
+
general:
|
4
|
+
config_upgrade_messages: |-
|
5
|
+
There were warnings and/or errors while loading your Vagrantfile.
|
6
|
+
Your Vagrantfile was written for an earlier version of Vagrant,
|
7
|
+
and while Vagrant does the best it can to remain backwards
|
8
|
+
compatible, there are some cases where things have changed
|
9
|
+
significantly enough to warrant a message. These messages are
|
10
|
+
shown below.
|
11
|
+
|
12
|
+
%{output}
|
13
|
+
moving_home_dir: "Moving old Vagrant home directory to new location: %{directory}"
|
14
|
+
home_dir_migration_failed: |-
|
15
|
+
Both an old and new Vagrant home directory exist. Only the new one will
|
16
|
+
be used. Please merge the old directory into the new directory if you'd
|
17
|
+
like to use the old data as well.
|
18
|
+
|
19
|
+
Old: %{old}
|
20
|
+
New: %{new}
|
21
|
+
not_in_installer: |-
|
22
|
+
You appear to be running Vagrant outside of the official installers.
|
23
|
+
Note that the installers are what ensure that Vagrant has all required
|
24
|
+
dependencies, and Vagrant assumes that these dependencies exist. By
|
25
|
+
running outside of the installer environment, Vagrant may not function
|
26
|
+
properly. To remove this warning, install Vagrant using one of the
|
27
|
+
official packages from vagrantup.com.
|
28
|
+
upgraded_v1_dotfile: |-
|
29
|
+
A Vagrant 1.0.x state file was found for this environment. Vagrant has
|
30
|
+
gone ahead and auto-upgraded this to the latest format. Everything
|
31
|
+
should continue working as normal. Beware, however, that older versions
|
32
|
+
of Vagrant may no longer be used with this environment.
|
33
|
+
|
34
|
+
However, in case anything went wrong, the old dotfile was backed up
|
35
|
+
to the location below. If everything is okay, it is safe to remove
|
36
|
+
this backup.
|
37
|
+
|
38
|
+
Backup: %{backup_path}
|
39
|
+
|
40
|
+
#-------------------------------------------------------------------------------
|
41
|
+
# Translations for exception classes
|
42
|
+
#-------------------------------------------------------------------------------
|
43
|
+
errors:
|
44
|
+
active_machine_with_different_provider: |-
|
45
|
+
An active machine was found with a different provider. Vagrant
|
46
|
+
currently allows each machine to be brought up with only a single
|
47
|
+
provider at a time. A future version will remove this limitation.
|
48
|
+
Until then, please destroy the existing machine to up with a new
|
49
|
+
provider.
|
50
|
+
|
51
|
+
Machine name: %{name}
|
52
|
+
Active provider: %{active_provider}
|
53
|
+
Requested provider: %{requested_provider}
|
54
|
+
base_vm_not_found: The base VM with the name '%{name}' was not found.
|
55
|
+
box_not_found: Box '%{name}' could not be found.
|
56
|
+
box_provider_doesnt_match: |-
|
57
|
+
The box you attempted to add doesn't match the provider you specified.
|
58
|
+
|
59
|
+
Provider expected: %{expected}
|
60
|
+
Provider of box: %{actual}
|
61
|
+
box_upgrade_required: |-
|
62
|
+
The box '%{name}' is still stored on disk in the Vagrant 1.0.x
|
63
|
+
format. This box must be upgraded in order to work properly with
|
64
|
+
this version of Vagrant.
|
65
|
+
cli_invalid_options: |-
|
66
|
+
An invalid option was specified. The help for this command
|
67
|
+
is available below.
|
68
|
+
|
69
|
+
%{help}
|
70
|
+
cli_invalid_usage: |-
|
71
|
+
This command was not invoked properly. The help for this command is
|
72
|
+
available below.
|
73
|
+
|
74
|
+
%{help}
|
75
|
+
config_invalid: |-
|
76
|
+
There are errors in the configuration of this machine. Please fix
|
77
|
+
the following errors and try again:
|
78
|
+
|
79
|
+
%{errors}
|
80
|
+
config_upgrade_errors: |-
|
81
|
+
Because there were errors upgrading your Vagrantfiles, Vagrant
|
82
|
+
can no longer continue. Please fix the errors above and try again.
|
83
|
+
copy_private_key_failed: |-
|
84
|
+
Vagrant failed to copy the default insecure private key into your
|
85
|
+
home directory. This is usually caused by a permissions error.
|
86
|
+
Please make sure the permissions of the source is readable and
|
87
|
+
the destination is writable.
|
88
|
+
|
89
|
+
Source: %{source}
|
90
|
+
Destination: %{destination}
|
91
|
+
destroy_requires_force: |-
|
92
|
+
Destroy doesn't have a TTY to ask for confirmation. Please pass the
|
93
|
+
`--force` flag to force a destroy, otherwise attach a TTY so that
|
94
|
+
the destroy can be confirmed.
|
95
|
+
dotfile_is_directory: |-
|
96
|
+
The local file Vagrant uses to store data ".vagrant" already exists
|
97
|
+
and is a directory! If you are in your home directory, then please run
|
98
|
+
this command in another directory. If you aren't in a home directory,
|
99
|
+
then please rename ".vagrant" to something else, or configure Vagrant
|
100
|
+
to use another filename by modifying `config.vagrant.dotfile_name`.
|
101
|
+
dotfile_upgrade_json_error: |-
|
102
|
+
A Vagrant 1.0.x local state file was found. Vagrant is able to upgrade
|
103
|
+
this to the latest format automatically, however various checks are
|
104
|
+
put in place to verify data isn't incorrectly deleted. In this case,
|
105
|
+
the old state file was not valid JSON. Vagrant 1.0.x would store state
|
106
|
+
as valid JSON, meaning that this file was probably tampered with or
|
107
|
+
manually edited. Vagrant's auto-upgrade process cannot continue in this
|
108
|
+
case.
|
109
|
+
|
110
|
+
In most cases, this can be resolve by simply removing the state file.
|
111
|
+
Note however though that if Vagrant was previously managing virtual
|
112
|
+
machines, they may be left in an "orphan" state. That is, if they are
|
113
|
+
running or exist, they'll have to manually be removed.
|
114
|
+
|
115
|
+
If you're unsure what to do, ask the Vagrant mailing list or contact
|
116
|
+
support.
|
117
|
+
|
118
|
+
State file path: %{state_file}
|
119
|
+
environment_locked: |-
|
120
|
+
An instance of Vagrant is already running. Only one instance of Vagrant
|
121
|
+
may run at any given time to avoid problems with VirtualBox inconsistencies
|
122
|
+
occurring. Please wait for the other instance of Vagrant to end and then
|
123
|
+
try again.
|
124
|
+
gem_command_in_bundler: |-
|
125
|
+
You cannot run the `vagrant plugin` command while in a bundler environment.
|
126
|
+
This should generally never happen unless Vagrant is installed outside
|
127
|
+
of the official installers or another gem is wrongly attempting to
|
128
|
+
use Vagrant internals directly. Please properly install Vagrant to
|
129
|
+
fix this. If this error persists, please contact support.
|
130
|
+
guest:
|
131
|
+
invalid_class: |-
|
132
|
+
The specified guest class does not inherit from a proper guest
|
133
|
+
component class. The guest class must inherit from this.
|
134
|
+
|
135
|
+
The specified guest class was: %{guest}
|
136
|
+
unknown_type: |-
|
137
|
+
The specified guest type is unknown: %{guest}. Please change this
|
138
|
+
to a proper value.
|
139
|
+
unspecified: |-
|
140
|
+
A VM guest type must be specified! This is done via the `config.vm.guest`
|
141
|
+
configuration value. Please read the documentation online for more information.
|
142
|
+
home_dir_not_accessible: |-
|
143
|
+
The home directory you specified is not accessible. The home
|
144
|
+
directory that Vagrant uses must be both readable and writable.
|
145
|
+
|
146
|
+
You specified: %{home_path}
|
147
|
+
interrupted: |-
|
148
|
+
Vagrant exited after cleanup due to external interrupt.
|
149
|
+
local_data_dir_not_accessible: |-
|
150
|
+
The directory Vagrant will use to store local environment-specific
|
151
|
+
state is not accessible. The directory specified as the local data
|
152
|
+
directory must be both readable and writable for the user that is
|
153
|
+
running Vagrant.
|
154
|
+
|
155
|
+
Local data directory: %{local_data_path}
|
156
|
+
machine_guest_not_ready: |-
|
157
|
+
Guest-specific operations were attempted on a machine that is not
|
158
|
+
ready for guest communication. This should not happen and a bug
|
159
|
+
should be reported.
|
160
|
+
machine_not_found: |-
|
161
|
+
The machine with the name '%{name}' was not found configured for
|
162
|
+
this Vagrant environment.
|
163
|
+
machine_state_invalid: |-
|
164
|
+
An internal error has occurred! The provider of the machine you're
|
165
|
+
trying to work with reported an invalid state. This is a bug with
|
166
|
+
the provider you're using, and not with Vagrant itself or with
|
167
|
+
any configuration you may have done. Please report this bug to
|
168
|
+
the proper location.
|
169
|
+
multi_vm_required: |-
|
170
|
+
A multi-vm environment is required for name specification to this command.
|
171
|
+
multi_vm_target_required: |-
|
172
|
+
This command requires a specific VM name to target in a multi-VM environment.
|
173
|
+
nfs_no_guest_ip: |-
|
174
|
+
No guest IP was given to the Vagrant core NFS helper. This is an
|
175
|
+
internal error that should be reported as a bug.
|
176
|
+
nfs_no_host_ip: |-
|
177
|
+
No host IP was given to the Vagrant core NFS helper. This is
|
178
|
+
an internal error that should be reported as a bug.
|
179
|
+
no_env: |-
|
180
|
+
A Vagrant environment is required to run this command. Run `vagrant init`
|
181
|
+
to set one up in this directory, or change to a directory with a
|
182
|
+
Vagrantfile and try again.
|
183
|
+
plugin_gem_error: |-
|
184
|
+
An error occurred within RubyGems, the underlying system used to
|
185
|
+
manage Vagrant plugins. The output of the errors are shown below:
|
186
|
+
|
187
|
+
%{output}
|
188
|
+
plugin_install_bad_entry_point: |-
|
189
|
+
Attempting to load the plugin '%{name}' failed, because
|
190
|
+
the entry point doesn't exist. The entry point attempted was
|
191
|
+
'%{entry_point}'. If this is not correct, please manually
|
192
|
+
specify an `--entry-point` when installing the plugin.
|
193
|
+
plugin_install_license_not_found: |-
|
194
|
+
The license file to install could not be found. Please verify
|
195
|
+
the path you gave is correct. The path to the license file given
|
196
|
+
was: '%{path}'
|
197
|
+
plugin_install_not_found: |-
|
198
|
+
The plugin '%{name}' could not be found in local or remote
|
199
|
+
repositories. Please check the name of the plugin and try again.
|
200
|
+
plugin_load_error: |-
|
201
|
+
The plugin "%{plugin}" could not be found. Please make sure that it is
|
202
|
+
properly installed via `vagrant plugin`. Note that plugins made for
|
203
|
+
Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
|
204
|
+
continue to show when you use `plugin install` with a 1.0.x plugin.
|
205
|
+
plugin_load_failed: |-
|
206
|
+
Failed to load the "%{plugin}" plugin. View logs for more details.
|
207
|
+
plugin_load_failed_with_output: |-
|
208
|
+
Failed to load the "%{plugin}" plugin. The output from loading
|
209
|
+
the plugin is shown below. View the logs for complete details.
|
210
|
+
|
211
|
+
stdout: %{stdout}
|
212
|
+
|
213
|
+
stderr: %{stderr}
|
214
|
+
plugin_not_found: |-
|
215
|
+
The plugin '%{name}' could not be found. Please install this plugin
|
216
|
+
prior to attempting to do anything with it.
|
217
|
+
port_collision_resume: |-
|
218
|
+
This VM cannot be resumed, because the forwarded ports would collide
|
219
|
+
with a running program (it could be another virtual machine). Normally,
|
220
|
+
Vagrant will attempt to fix this for you but VirtualBox only allows
|
221
|
+
forwarded ports to change if the VM is powered off. Therefore, please
|
222
|
+
reload your VM or stop the other program to continue.
|
223
|
+
provider_not_found: |-
|
224
|
+
The provider '%{provider}' could not be found, but was requested to
|
225
|
+
back the machine '%{machine}'. Please use a provider that exists.
|
226
|
+
scp_permission_denied: |-
|
227
|
+
Failed to upload a file to the guest VM via SCP due to a permissions
|
228
|
+
error. This is normally because the user running Vagrant doesn't have
|
229
|
+
read permission on the file. Please set proper permissions on the file:
|
230
|
+
|
231
|
+
%{path}
|
232
|
+
scp_unavailable: |-
|
233
|
+
SSH server on the guest doesn't support SCP. Please install the necessary
|
234
|
+
software to enable SCP on your guest operating system.
|
235
|
+
shared_folder_create_failed: |-
|
236
|
+
Failed to create the following shared folder on the host system. This is
|
237
|
+
usually because Vagrant does not have sufficient permissions to create
|
238
|
+
the folder.
|
239
|
+
|
240
|
+
%{path}
|
241
|
+
|
242
|
+
Please create the folder manually or specify another path to share.
|
243
|
+
ssh_authentication_failed: |-
|
244
|
+
SSH authentication failed! This is typically caused by the public/private
|
245
|
+
keypair for the SSH user not being properly set on the guest VM. Please
|
246
|
+
verify that the guest VM is setup with the proper public key, and that
|
247
|
+
the private key path for Vagrant is setup properly as well.
|
248
|
+
ssh_bad_exit_status: |-
|
249
|
+
The following SSH command responded with a non-zero exit status.
|
250
|
+
Vagrant assumes that this means the command failed!
|
251
|
+
|
252
|
+
%{command}
|
253
|
+
ssh_connection_refused: |-
|
254
|
+
SSH connection was refused! This usually happens if the VM failed to
|
255
|
+
boot properly. Some steps to try to fix this: First, try reloading your
|
256
|
+
VM with `vagrant reload`, since a simple restart sometimes fixes things.
|
257
|
+
If that doesn't work, destroy your VM and recreate it with a `vagrant destroy`
|
258
|
+
followed by a `vagrant up`. If that doesn't work, contact a Vagrant
|
259
|
+
maintainer (support channels listed on the website) for more assistance.
|
260
|
+
ssh_connection_reset: |-
|
261
|
+
SSH connection was reset! This usually happens when the machine is
|
262
|
+
taking too long to reboot. First, try reloading your machine with
|
263
|
+
`vagrant reload`, since a simple restart sometimes fixes things.
|
264
|
+
If that doesn't work, destroy your machine and recreate it with
|
265
|
+
a `vagrant destroy` followed by a `1vagrant up`. If that doesn't work,
|
266
|
+
contact support.
|
267
|
+
ssh_connection_timeout: |-
|
268
|
+
Vagrant timed out while attempting to connect via SSH. This usually
|
269
|
+
means that the VM booted, but there are issues with the SSH configuration
|
270
|
+
or network connectivity issues. Please try to `vagrant reload` or
|
271
|
+
`vagrant up` again.
|
272
|
+
ssh_disconnected: |-
|
273
|
+
The SSH connection was unexpectedly closed by the remote end. This
|
274
|
+
usually indicates that SSH within the guest machine was unable to
|
275
|
+
properly start up. Please boot the VM in GUI mode to check whether
|
276
|
+
it is booting properly.
|
277
|
+
ssh_host_down: |-
|
278
|
+
While attempting to connect with SSH, a "host is down" (EHOSTDOWN)
|
279
|
+
error was received. Please verify your SSH settings are correct
|
280
|
+
and try again.
|
281
|
+
ssh_key_bad_permissions: |-
|
282
|
+
The private key to connect to this box via SSH has invalid permissions
|
283
|
+
set on it. The permissions of the private key should be set to 0600, otherwise SSH will
|
284
|
+
ignore the key. Vagrant tried to do this automatically for you but failed. Please set the
|
285
|
+
permissions on the following file to 0600 and then try running this command again:
|
286
|
+
|
287
|
+
%{key_path}
|
288
|
+
ssh_key_type_not_supported: |-
|
289
|
+
The private key you're attempting to use with this Vagrant box uses
|
290
|
+
an unsupported encryption type. The SSH library Vagrant uses does not support
|
291
|
+
this key type. Please use `ssh-rsa` or `ssh-dss` instead. Note that
|
292
|
+
sometimes keys in your ssh-agent can interfere with this as well,
|
293
|
+
so verify the keys are valid there in addition to standard
|
294
|
+
file paths.
|
295
|
+
ssh_not_ready: |-
|
296
|
+
The provider for this Vagrant-managed machine is reporting that it
|
297
|
+
is not yet ready for SSH. Depending on your provider this can carry
|
298
|
+
different meanings. Make sure your machine is created and running and
|
299
|
+
try again. Additionally, check the output of `vagrant status` to verify
|
300
|
+
that the machine is in the state that you expect. If you continue to
|
301
|
+
get this error message, please view the documentation for the provider
|
302
|
+
you're using.
|
303
|
+
ssh_port_not_detected: |-
|
304
|
+
Vagrant couldn't determine the SSH port for your VM! Vagrant attempts to
|
305
|
+
automatically find a forwarded port that matches your `config.ssh.guest_port`
|
306
|
+
(default: 22) value and uses this for SSH. Alternatively, if `config.ssh.port`
|
307
|
+
is set, it will use this.
|
308
|
+
|
309
|
+
However, in this case Vagrant was unable to find a forwarded port that matches
|
310
|
+
the guest port and `config.ssh.port` is not set!
|
311
|
+
|
312
|
+
Please make sure that you have a forwarded port that goes to the configured
|
313
|
+
guest port value, or specify an explicit SSH port with `config.ssh.port`.
|
314
|
+
ssh_unavailable: "`ssh` binary could not be found. Is an SSH client installed?"
|
315
|
+
ssh_unavailable_windows: |-
|
316
|
+
`ssh` executable not found in any directories in the %PATH% variable. Is an
|
317
|
+
SSH client installed? Try installing Cygwin, MinGW or Git, all of which
|
318
|
+
contain an SSH client. Or use the PuTTY SSH client with the following
|
319
|
+
authentication information shown below:
|
320
|
+
|
321
|
+
Host: %{host}
|
322
|
+
Port: %{port}
|
323
|
+
Username: %{username}
|
324
|
+
Private key: %{key_path}
|
325
|
+
ui_expects_tty: |-
|
326
|
+
Vagrant is attempting to interface with the UI in a way that requires
|
327
|
+
a TTY. Most actions in Vagrant that require a TTY have configuration
|
328
|
+
switches to disable this requirement. Please do that or run Vagrant
|
329
|
+
with TTY.
|
330
|
+
unimplemented_provider_action: |-
|
331
|
+
Vagrant attempted to call the action '%{action}' on the provider
|
332
|
+
'%{provider}', but this provider doesn't support this action. This
|
333
|
+
is probably a bug in either the provider or the plugin calling this
|
334
|
+
action, and should be reported.
|
335
|
+
vagrantfile_exists: |-
|
336
|
+
`Vagrantfile` already exists in this directory. Remove it before
|
337
|
+
running `vagrant init`.
|
338
|
+
vagrantfile_load_error: |-
|
339
|
+
There was an error loading a Vagrantfile. The file being loaded
|
340
|
+
and the error message are shown below. This is usually caused by
|
341
|
+
a syntax error.
|
342
|
+
|
343
|
+
Path: %{path}
|
344
|
+
Message: %{message}
|
345
|
+
vagrantfile_syntax_error: |-
|
346
|
+
There is a syntax error in the following Vagrantfile. The syntax error
|
347
|
+
message is reproduced below for convenience:
|
348
|
+
|
349
|
+
%{file}
|
350
|
+
vboxmanage_error: |-
|
351
|
+
There was an error executing the following command with VBoxManage:
|
352
|
+
|
353
|
+
%{command}
|
354
|
+
|
355
|
+
For more information on the failure, enable detailed logging by setting
|
356
|
+
the environment variable VAGRANT_LOG to DEBUG.
|
357
|
+
virtualbox_invalid_version: |-
|
358
|
+
Vagrant has detected that you have a version of VirtualBox installed
|
359
|
+
that is not supported. Please install one of the supported versions
|
360
|
+
listed below to use Vagrant:
|
361
|
+
|
362
|
+
%{supported_versions}
|
363
|
+
virtualbox_kernel_module_not_loaded: |-
|
364
|
+
VirtualBox is complaining that the kernel module is not loaded. Please
|
365
|
+
run `VBoxManage --version` to see the error message which should contain
|
366
|
+
instructions on how to fix this error.
|
367
|
+
virtualbox_install_incomplete: |-
|
368
|
+
VirtualBox is complaining that the installation is incomplete. Please
|
369
|
+
run `VBoxManage --version` to see the error message which should contain
|
370
|
+
instructions on how to fix this error.
|
371
|
+
virtualbox_no_room_for_high_level_network: |-
|
372
|
+
There is no available slots on the VirtualBox VM for the configured
|
373
|
+
high-level network interfaces. "private_network" and "public_network"
|
374
|
+
network configurations consume a single network adapter slot on the
|
375
|
+
VirtualBox VM. VirtualBox limits the number of slots to 8, and it
|
376
|
+
appears that every slot is in use. Please lower the number of used
|
377
|
+
network adapters.
|
378
|
+
virtualbox_not_detected: |-
|
379
|
+
Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
|
380
|
+
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
|
381
|
+
this to be available on the PATH. If VirtualBox is installed, please find the
|
382
|
+
`VBoxManage` binary and add it to the PATH environmental variable.
|
383
|
+
vm_creation_required: |-
|
384
|
+
VM must be created before running this command. Run `vagrant up` first.
|
385
|
+
vm_inaccessible: |-
|
386
|
+
Your VM has become "inaccessible." Unfortunately, this is a critical error
|
387
|
+
with VirtualBox that Vagrant can not cleanly recover from. Please open VirtualBox
|
388
|
+
and clear out your inaccessible virtual machines or find a way to fix
|
389
|
+
them.
|
390
|
+
vm_name_exists: |-
|
391
|
+
A VirtualBox machine with the name '%{name}' already exists.
|
392
|
+
Please use another name or delete the machine with the existing
|
393
|
+
name, and try again.
|
394
|
+
vm_no_match: |-
|
395
|
+
No virtual machines matched the regular expression given.
|
396
|
+
vm_not_found: |-
|
397
|
+
A VM by the name of %{name} was not found.
|
398
|
+
vm_not_running: |-
|
399
|
+
VM must be running to open SSH connection. Run `vagrant up`
|
400
|
+
to start the virtual machine.
|
401
|
+
|
402
|
+
#-------------------------------------------------------------------------------
|
403
|
+
# Translations for config validation errors
|
404
|
+
#-------------------------------------------------------------------------------
|
405
|
+
config:
|
406
|
+
common:
|
407
|
+
error_empty: "`%{field}` must be not be empty."
|
408
|
+
chef:
|
409
|
+
cookbooks_path_empty: "Must specify a cookbooks path for chef solo."
|
410
|
+
cookbooks_path_missing: |-
|
411
|
+
Cookbook path doesn't exist: %{path}
|
412
|
+
run_list_empty: "Run list must not be empty."
|
413
|
+
server_url_empty: "Chef server URL must be populated."
|
414
|
+
validation_key_path: "Validation key path must be valid path to your chef server validation key."
|
415
|
+
loader:
|
416
|
+
bad_v1_key: |-
|
417
|
+
Unknown configuration section '%{key}'. If this section was part of
|
418
|
+
a Vagrant 1.0.x plugin, note that 1.0.x plugins are incompatible with 1.1+.
|
419
|
+
root:
|
420
|
+
bad_key: |-
|
421
|
+
Unknown configuration section '%{key}'.
|
422
|
+
ssh:
|
423
|
+
private_key_missing: "`private_key_path` file must exist: %{path}"
|
424
|
+
vm:
|
425
|
+
base_mac_invalid: "Base MAC address for eth0/NAT must be set. Contact box maintainer for more information."
|
426
|
+
box_missing: "A box must be specified."
|
427
|
+
box_not_found: "The box '%{name}' could not be found."
|
428
|
+
hostname_invalid_characters: |-
|
429
|
+
The hostname set for the VM should only contain letters, numbers,
|
430
|
+
and hyphens.
|
431
|
+
network_invalid: |-
|
432
|
+
The network type '%{type}' is not valid. Please use
|
433
|
+
'hostonly' or 'bridged'.
|
434
|
+
network_ip_required: |-
|
435
|
+
Host only networks require an IP as an argument.
|
436
|
+
network_ip_invalid: |-
|
437
|
+
The host only network IP '%{ip}' is invalid.
|
438
|
+
network_ip_ends_one: |-
|
439
|
+
The host only network IP '%{ip}' must not end in a 1, as this
|
440
|
+
is reserved for the host machine.
|
441
|
+
nfs_not_supported: |-
|
442
|
+
It appears your machine doesn't support NFS, or there is not an
|
443
|
+
adapter to enable NFS on this machine for Vagrant. Please verify
|
444
|
+
that `nfsd` is installed on your machine, and try again. If you're
|
445
|
+
on Windows, NFS isn't supported. If the problem persists, please
|
446
|
+
contact Vagrant support.
|
447
|
+
nfs_requires_host: |-
|
448
|
+
Using NFS shared folders requires a host to be specified
|
449
|
+
using `config.vagrant.host`.
|
450
|
+
network_fp_requires_ports: |-
|
451
|
+
Forwarded port definitions require a "host" and "guest" value
|
452
|
+
shared_folder_hostpath_missing: |-
|
453
|
+
The host path of the shared folder is missing: %{path}
|
454
|
+
shared_folder_nfs_owner_group: |-
|
455
|
+
Shared folder that have NFS enabled do no support owner/group
|
456
|
+
attributes. Host path: %{path}
|
457
|
+
provisioner_not_found: "The provisioner '%{shortcut}' doesn't exist."
|
458
|
+
provisioner_invalid_class: |-
|
459
|
+
The provisioner '%{shortcut}' must inherit from
|
460
|
+
`Vagrant::Plugin::V1::Provisioner`."
|
461
|
+
|
462
|
+
#-------------------------------------------------------------------------------
|
463
|
+
# Translations for commands. e.g. `vagrant x`
|
464
|
+
#-------------------------------------------------------------------------------
|
465
|
+
commands:
|
466
|
+
common:
|
467
|
+
vm_not_created: "VM not created. Moving on..."
|
468
|
+
vm_not_running: "VM is not currently running. Please bring it up to run this command."
|
469
|
+
box:
|
470
|
+
no_installed_boxes: "There are no installed boxes! Use `vagrant box add` to add some."
|
471
|
+
removing: |-
|
472
|
+
Removing box '%{name}' with provider '%{provider}'...
|
473
|
+
destroy:
|
474
|
+
confirmation: "Are you sure you want to destroy the '%{name}' VM? [y/N] "
|
475
|
+
will_not_destroy: |-
|
476
|
+
The VM '%{name}' will not be destroyed, since the confirmation
|
477
|
+
was declined.
|
478
|
+
init:
|
479
|
+
success: |-
|
480
|
+
A `Vagrantfile` has been placed in this directory. You are now
|
481
|
+
ready to `vagrant up` your first virtual environment! Please read
|
482
|
+
the comments in the Vagrantfile as well as documentation on
|
483
|
+
`vagrantup.com` for more information on using Vagrant.
|
484
|
+
plugin:
|
485
|
+
installed_license: |-
|
486
|
+
The license for '%{name}' was successfully installed!
|
487
|
+
installing_license: |-
|
488
|
+
Installing license for '%{name}'...
|
489
|
+
no_plugins: |-
|
490
|
+
No plugins installed.
|
491
|
+
installed: |-
|
492
|
+
Installed the plugin '%{name} (%{version})'!
|
493
|
+
installing: |-
|
494
|
+
Installing the '%{name}' plugin. This can take a few minutes...
|
495
|
+
uninstalling: |-
|
496
|
+
Uninstalling the '%{name}' plugin...
|
497
|
+
status:
|
498
|
+
aborted: |-
|
499
|
+
The VM is in an aborted state. This means that it was abruptly
|
500
|
+
stopped without properly closing the session. Run `vagrant up`
|
501
|
+
to resume this virtual machine. If any problems persist, you may
|
502
|
+
have to destroy and restart the virtual machine.
|
503
|
+
gurumeditation: |-
|
504
|
+
The VM is in the "guru meditation" state. This is a rare case which means
|
505
|
+
that an internal error in VitualBox caused the VM to fail. This is always
|
506
|
+
the sign of a bug in VirtualBox. You can try to bring your VM back online
|
507
|
+
with a `vagrant up`.
|
508
|
+
inaccessible: |-
|
509
|
+
The VM is inaccessible! This is a rare case which means that VirtualBox
|
510
|
+
can't find your VM configuration. This usually happens when upgrading
|
511
|
+
VirtualBox, moving to a new computer, etc. Please consult VirtualBox
|
512
|
+
for how to handle this issue.
|
513
|
+
output: |-
|
514
|
+
Current machine states:
|
515
|
+
|
516
|
+
%{states}
|
517
|
+
|
518
|
+
%{message}
|
519
|
+
not_created: |-
|
520
|
+
The environment has not yet been created. Run `vagrant up` to
|
521
|
+
create the environment. If a machine is not created, only the
|
522
|
+
default provider will be shown. So if a provider is not listed,
|
523
|
+
then the machine is not created for that environment.
|
524
|
+
paused: |-
|
525
|
+
The VM is paused. This VM may have been paused via the VirtualBox
|
526
|
+
GUI or the VBoxManage command line interface. To unpause, please
|
527
|
+
use the VirtualBox GUI and/or VBoxManage command line interface so
|
528
|
+
that vagrant would be able to control the VM again.
|
529
|
+
poweroff: |-
|
530
|
+
The VM is powered off. To restart the VM, simply run `vagrant up`
|
531
|
+
running: |-
|
532
|
+
The VM is running. To stop this VM, you can run `vagrant halt` to
|
533
|
+
shut it down forcefully, or you can run `vagrant suspend` to simply
|
534
|
+
suspend the virtual machine. In either case, to restart it again,
|
535
|
+
simply run `vagrant up`.
|
536
|
+
saving: |-
|
537
|
+
The VM is currently saving its state. In a few moments this state
|
538
|
+
should transition to "saved." Please run `vagrant status` again
|
539
|
+
in a few seconds.
|
540
|
+
saved: |-
|
541
|
+
To resume this VM, simply run `vagrant up`.
|
542
|
+
stuck: |-
|
543
|
+
The VM is "stuck!" This is a very rare state which means that
|
544
|
+
VirtualBox is unable to recover the current state of the VM.
|
545
|
+
The only known solution to this problem is to restart your
|
546
|
+
machine, sorry.
|
547
|
+
listing: |-
|
548
|
+
This environment represents multiple VMs. The VMs are all listed
|
549
|
+
above with their current state. For more information about a specific
|
550
|
+
VM, run `vagrant status NAME`.
|
551
|
+
up:
|
552
|
+
upping: |-
|
553
|
+
Bringing machine '%{name}' up with '%{provider}' provider...
|
554
|
+
version:
|
555
|
+
output: "Vagrant version %{version}"
|
556
|
+
|
557
|
+
#-------------------------------------------------------------------------------
|
558
|
+
# Translations for Vagrant middleware acions
|
559
|
+
#-------------------------------------------------------------------------------
|
560
|
+
actions:
|
561
|
+
runner:
|
562
|
+
waiting_cleanup: "Waiting for cleanup before exiting..."
|
563
|
+
exit_immediately: "Exiting immediately, without cleanup!"
|
564
|
+
vm:
|
565
|
+
boot:
|
566
|
+
booting: Booting VM...
|
567
|
+
waiting: Waiting for VM to boot. This can take a few minutes.
|
568
|
+
ready: VM booted and ready for use!
|
569
|
+
failed: Failed to connect to VM!
|
570
|
+
failed_to_boot: |-
|
571
|
+
Failed to connect to VM via SSH. Please verify the VM successfully booted
|
572
|
+
by looking at the VirtualBox GUI.
|
573
|
+
failed_to_run: |-
|
574
|
+
The VM failed to remain in the "running" state while attempting to boot.
|
575
|
+
This is normally caused by a misconfiguration or host system incompatibilities.
|
576
|
+
Please open the VirtualBox GUI and attempt to boot the virtual machine
|
577
|
+
manually to get a more informative error message.
|
578
|
+
bridged_networking:
|
579
|
+
available: |-
|
580
|
+
Available bridged network interfaces:
|
581
|
+
bridging: |-
|
582
|
+
Bridging adapter #%{adapter} to '%{bridge}'
|
583
|
+
enabling: |-
|
584
|
+
Enabling bridged network...
|
585
|
+
preparing: |-
|
586
|
+
Preparing bridged networking...
|
587
|
+
specific_not_found: |-
|
588
|
+
Specific bridge '%{bridge}' not found. You may be asked to specify
|
589
|
+
which network to bridge to.
|
590
|
+
check_box:
|
591
|
+
not_found: |-
|
592
|
+
Box '%{name}' was not found. Fetching box from specified URL for
|
593
|
+
the provider '%{provider}'. Note that if the URL does not have
|
594
|
+
a box for this provider, you should interrupt Vagrant now and add
|
595
|
+
the box yourself. Otherwise Vagrant will attempt to download the
|
596
|
+
full box prior to discovering this error.
|
597
|
+
not_specified: |-
|
598
|
+
No base box was specified! A base box is required as a staring point
|
599
|
+
for every vagrant virtual machine. Please specify one in your Vagrantfile
|
600
|
+
using `config.vm.box`
|
601
|
+
does_not_exist: |-
|
602
|
+
Specified box `%{name}` does not exist!
|
603
|
+
|
604
|
+
The box must be added through the `vagrant box add` command. Please view
|
605
|
+
the documentation associated with the command for more information.
|
606
|
+
check_guest_additions:
|
607
|
+
not_detected: |-
|
608
|
+
No guest additions were detected on the base box for this VM! Guest
|
609
|
+
additions are required for forwarded ports, shared folders, host only
|
610
|
+
networking, and more. If SSH fails on this machine, please install
|
611
|
+
the guest additions and repackage the box to continue.
|
612
|
+
|
613
|
+
This is not an error message; everything may continue to work properly,
|
614
|
+
in which case you may ignore this message.
|
615
|
+
version_mismatch: |-
|
616
|
+
The guest additions on this VM do not match the installed version of
|
617
|
+
VirtualBox! In most cases this is fine, but in rare cases it can
|
618
|
+
cause things such as shared folders to not work properly. If you see
|
619
|
+
shared folder errors, please update the guest additions within the
|
620
|
+
virtual machine and reload your VM.
|
621
|
+
|
622
|
+
Guest Additions Version: %{guest_version}
|
623
|
+
VirtualBox Version: %{virtualbox_version}
|
624
|
+
clear_forward_ports:
|
625
|
+
deleting: Clearing any previously set forwarded ports...
|
626
|
+
clear_network_interfaces:
|
627
|
+
deleting: Clearing any previously set network interfaces...
|
628
|
+
clear_shared_folders:
|
629
|
+
deleting: Cleaning previously set shared folders...
|
630
|
+
customize:
|
631
|
+
failure: |-
|
632
|
+
A customization command failed:
|
633
|
+
|
634
|
+
%{command}
|
635
|
+
|
636
|
+
The following error was experienced:
|
637
|
+
|
638
|
+
%{error}
|
639
|
+
|
640
|
+
Please fix this customization and try again.
|
641
|
+
running: Running any VM customizations...
|
642
|
+
destroy:
|
643
|
+
destroying: Destroying VM and associated drives...
|
644
|
+
destroy_network:
|
645
|
+
destroying: Destroying unused networking interface...
|
646
|
+
disable_networks:
|
647
|
+
disabling: Disabling host only networks...
|
648
|
+
discard_state:
|
649
|
+
discarding: Discarding saved state of VM...
|
650
|
+
export:
|
651
|
+
create_dir: Creating temporary directory for export...
|
652
|
+
exporting: Exporting VM...
|
653
|
+
power_off: "The Vagrant virtual environment you are trying to package must be powered off."
|
654
|
+
forward_ports:
|
655
|
+
auto_empty: |-
|
656
|
+
Vagrant found a port collision for the specified port and virtual machine.
|
657
|
+
While this port was marked to be auto-corrected, the ports in the
|
658
|
+
auto-correction range are all also used.
|
659
|
+
|
660
|
+
VM: %{vm_name}
|
661
|
+
Forwarded port: %{guest_port} => %{host_port}
|
662
|
+
collision_error: |-
|
663
|
+
Vagrant cannot forward the specified ports on this VM, since they
|
664
|
+
would collide with some other application that is already listening
|
665
|
+
on these ports. The forwarded port to %{host_port} is already in use
|
666
|
+
on the host machine.
|
667
|
+
|
668
|
+
To fix this, modify your current projects Vagrantfile to use another
|
669
|
+
port. Example, where '1234' would be replaced by a unique host port:
|
670
|
+
|
671
|
+
config.vm.network :forwarded_port, guest: %{guest_port}, host: 1234
|
672
|
+
|
673
|
+
Sometimes, Vagrant will attempt to auto-correct this for you. In this
|
674
|
+
case, Vagrant was unable to. This is usually because the guest machine
|
675
|
+
is in a state which doesn't allow modifying port forwarding.
|
676
|
+
fixed_collision: |-
|
677
|
+
Fixed port collision for %{guest_port} => %{host_port}. Now on port %{new_port}.
|
678
|
+
forwarding: Forwarding ports...
|
679
|
+
forwarding_entry: |-
|
680
|
+
-- %{guest_port} => %{host_port} (adapter %{adapter})
|
681
|
+
non_nat: |-
|
682
|
+
VirtualBox adapter #%{adapter} not configured as "NAT". Skipping port
|
683
|
+
forwards on this adapter.
|
684
|
+
privileged_ports: |-
|
685
|
+
You are trying to forward to privileged ports (ports <= 1024). Most
|
686
|
+
operating systems restrict this to only privileged process (typically
|
687
|
+
processes running as an administrative user). This is a warning in case
|
688
|
+
the port forwarding doesn't work. If any problems occur, please try a
|
689
|
+
port higher than 1024.
|
690
|
+
halt:
|
691
|
+
force: |-
|
692
|
+
Forcing shutdown of VM...
|
693
|
+
graceful: |-
|
694
|
+
Attempting graceful shutdown of VM...
|
695
|
+
hostname:
|
696
|
+
setting: "Setting hostname..."
|
697
|
+
import:
|
698
|
+
importing: Importing base box '%{name}'...
|
699
|
+
failure: |-
|
700
|
+
The VM import failed! Try running `VBoxManage import` on the box file
|
701
|
+
manually for more verbose error output.
|
702
|
+
match_mac:
|
703
|
+
matching: Matching MAC address for NAT networking...
|
704
|
+
no_base_mac: |-
|
705
|
+
No base MAC address was specified. This is required for the NAT networking
|
706
|
+
to work properly (and hence port forwarding, SSH, etc.). Specifying this
|
707
|
+
MAC address is typically up to the box and box maintiner. Please contact
|
708
|
+
the relevant person to solve this issue.
|
709
|
+
network:
|
710
|
+
adapter_collision: |-
|
711
|
+
More than one network have been assigned to the same adapter. Please
|
712
|
+
make sure your networks you've configured in your Vagrantfile do not
|
713
|
+
overlap.
|
714
|
+
configuring: |-
|
715
|
+
Configuring and enabling network interfaces...
|
716
|
+
dhcp_already_attached: |-
|
717
|
+
A host only network interface you're attempting to configure via DHCP
|
718
|
+
already has a conflicting host only adapter with DHCP enabled. The
|
719
|
+
DHCP on this adapter is incompatible with the DHCP settings. Two
|
720
|
+
host only network interfaces are not allowed to overlap, and each
|
721
|
+
host only network interface can have only one DHCP server. Please
|
722
|
+
reconfigure your host only network or remove the virtual machine
|
723
|
+
using the other host only network.
|
724
|
+
no_adapters: |-
|
725
|
+
No available adapters on the virtual machine were found to accomodate
|
726
|
+
for all configured networks. VirtualBox virtual machines have 8
|
727
|
+
network interfaces available usually, so please lower the number of
|
728
|
+
networks to below 8.
|
729
|
+
preparing: |-
|
730
|
+
Preparing network interfaces based on configuration...
|
731
|
+
host_only_network:
|
732
|
+
collides: |-
|
733
|
+
The specified host network collides with a non-hostonly network!
|
734
|
+
This will cause your specified IP to be inaccessible. Please change
|
735
|
+
the IP or name of your host only network to not match that of
|
736
|
+
a bridged or non-hostonly network.
|
737
|
+
creating: "Creating new host only network for environment..."
|
738
|
+
enabling: "Enabling host only network..."
|
739
|
+
not_found: |-
|
740
|
+
The specified host network could not be found: '%{name}.'
|
741
|
+
If the name specification is removed, Vagrant will create a new
|
742
|
+
host only network for you. Alternatively, please create the
|
743
|
+
specified network manually.
|
744
|
+
preparing: "Preparing host only network..."
|
745
|
+
nfs:
|
746
|
+
exporting: Exporting NFS shared folders...
|
747
|
+
mounting: Mounting NFS shared folders...
|
748
|
+
persist:
|
749
|
+
dotfile_error: |-
|
750
|
+
The dotfile which Vagrant uses to store the UUID of the project's
|
751
|
+
virtual machine already exists and is not a file! The dotfile is
|
752
|
+
currently configured to be '%{dotfile_path}'
|
753
|
+
|
754
|
+
To change this value, please see `config.vagrant.dotfile_name`
|
755
|
+
|
756
|
+
Are you trying to use Vagrant from your home directory? This is the
|
757
|
+
leading cause of this error message. To resolve this, simply use a
|
758
|
+
different directory. Or, if you really want to run Vagrant from your
|
759
|
+
home directory, modify the `config.vagrant.dotfile_name` configuration
|
760
|
+
key.
|
761
|
+
persisting: "Persisting the VM UUID (%{uuid})..."
|
762
|
+
provision:
|
763
|
+
beginning: "Running provisioner: %{provisioner}..."
|
764
|
+
resume:
|
765
|
+
resuming: Resuming suspended VM...
|
766
|
+
unpausing: |-
|
767
|
+
Unpausing the VM...
|
768
|
+
share_folders:
|
769
|
+
creating: Creating shared folders metadata...
|
770
|
+
mounting: Mounting shared folders...
|
771
|
+
mounting_entry: "-- %{guest_path}"
|
772
|
+
nomount_entry: "-- Automounting disabled: %{host_path}"
|
773
|
+
set_name:
|
774
|
+
setting_name: |-
|
775
|
+
Setting the name of the VM...
|
776
|
+
suspend:
|
777
|
+
suspending: Saving VM state and suspending execution...
|
778
|
+
|
779
|
+
box:
|
780
|
+
unpackage:
|
781
|
+
untar_failure: |-
|
782
|
+
The box failed to unpackage properly. Please verify that the box
|
783
|
+
file you're trying to add is not corrupted and try again. The
|
784
|
+
output from attempting to unpackage (if any):
|
785
|
+
|
786
|
+
%{output}
|
787
|
+
already_exists: |-
|
788
|
+
The box you're attempting to add already exits:
|
789
|
+
|
790
|
+
Name: %{name}
|
791
|
+
Provider: %{provider}
|
792
|
+
add:
|
793
|
+
adding: |-
|
794
|
+
Extracting box...
|
795
|
+
destroy:
|
796
|
+
destroying: "Deleting box '%{name}'..."
|
797
|
+
download:
|
798
|
+
with: "Downloading with %{class}..."
|
799
|
+
cleaning: "Cleaning up downloaded box..."
|
800
|
+
unknown_type: "Unknown or unsupported URI type given for box download."
|
801
|
+
verify:
|
802
|
+
verifying: "Verifying box..."
|
803
|
+
failed: |-
|
804
|
+
The box file you're attempting to add is invalid. This can be
|
805
|
+
commonly attributed to typos in the path given to the box add
|
806
|
+
command. Another common case of this is invalid packaging of the
|
807
|
+
box itself.
|
808
|
+
|
809
|
+
general:
|
810
|
+
package:
|
811
|
+
packaging: "Packaging additional file: %{file}"
|
812
|
+
compressing: "Compressing package to: %{tar_path}"
|
813
|
+
output_exists: |-
|
814
|
+
The specified file to save the package as already exists. Please
|
815
|
+
remove this file or specify a different file name for outputting.
|
816
|
+
output_is_directory: |-
|
817
|
+
The specified output is a directory. Please specify a path including
|
818
|
+
a filename.
|
819
|
+
requires_directory: |-
|
820
|
+
A directory was not specified to package. This should never happen
|
821
|
+
and is a result of an internal inconsistency.
|
822
|
+
include_file_missing: |-
|
823
|
+
Package include file doesn't exist: %{file}
|
824
|
+
|
825
|
+
downloaders:
|
826
|
+
file:
|
827
|
+
download: "Copying box to temporary location..."
|
828
|
+
file_missing: "The specified path to a file doesn't exist."
|
829
|
+
http:
|
830
|
+
connection_reset: |-
|
831
|
+
The remote server unexpectedly closed the connection. Vagrant was
|
832
|
+
unable to finish downloading the box. Please try again. If this
|
833
|
+
problem persists, please try downloading the box manually outside
|
834
|
+
of Vagrant, then adding the box from the filesystem.
|
835
|
+
connection_timeout: |-
|
836
|
+
Vagrant timed out while attempting to connect to the HTTP host.
|
837
|
+
Please check your internet and proxy settings and try again.
|
838
|
+
download: "Downloading box: %{url}"
|
839
|
+
socket_error: |-
|
840
|
+
An error occurred while trying to download the specified box. This most
|
841
|
+
often happens if there is no internet connection or the address is
|
842
|
+
invalid.
|
843
|
+
status_error: |-
|
844
|
+
Bad status code: %{status}
|
845
|
+
|
846
|
+
Please verify that the box exists and is accessible. Also verify that
|
847
|
+
this computer is properly connected to the internet.
|
848
|
+
|
849
|
+
hosts:
|
850
|
+
bsd:
|
851
|
+
nfs_export: |-
|
852
|
+
Preparing to edit /etc/exports. Administrator privileges will be required...
|
853
|
+
nfs_prune: |-
|
854
|
+
Pruning invalid NFS exports. Administrator privileges will be required...
|
855
|
+
linux:
|
856
|
+
nfs_export: |-
|
857
|
+
Preparing to edit /etc/exports. Administrator privileges will be required...
|
858
|
+
nfs_prune: |-
|
859
|
+
Pruning invalid NFS exports. Administrator privileges will be required...
|
860
|
+
arch:
|
861
|
+
nfs_export:
|
862
|
+
prepare: "Preparing to edit /etc/exports. Administrator privileges will be required..."
|
863
|
+
freebsd:
|
864
|
+
nfs_whitespace: |-
|
865
|
+
FreeBSD hosts do not support sharing directories with whitespace in
|
866
|
+
their path. Please adjust your path accordingly.
|
867
|
+
|
868
|
+
provisioners:
|
869
|
+
chef:
|
870
|
+
chef_not_detected: |-
|
871
|
+
The chef binary (either `chef-solo` or `chef-client`) was not found on
|
872
|
+
the VM and is required for chef provisioning. Please verify that chef
|
873
|
+
is installed and that the binary is available on the PATH.
|
874
|
+
json: "Generating chef JSON and uploading..."
|
875
|
+
client_key_folder: "Creating folder to hold client key..."
|
876
|
+
upload_validation_key: "Uploading chef client validation key..."
|
877
|
+
upload_encrypted_data_bag_secret_key: "Uploading chef encrypted data bag secret key..."
|
878
|
+
running_client: "Running chef-client..."
|
879
|
+
running_client_again: "Running chef-client again (failed to converge)..."
|
880
|
+
running_solo: "Running chef-solo..."
|
881
|
+
running_solo_again: "Running chef-solo again (failed to converge)..."
|
882
|
+
missing_shared_folders: |-
|
883
|
+
Shared folders that Chef requires are missing on the virtual machine.
|
884
|
+
This is usually due to configuration changing after already booting the
|
885
|
+
machine. The fix is to run a `vagrant reload` so that the proper shared
|
886
|
+
folders will be prepared and mounted on the VM.
|
887
|
+
no_convergence: |-
|
888
|
+
Chef never successfully completed! Any errors should be visible in the
|
889
|
+
output above. Please fix your recipes so that they properly complete.
|
890
|
+
not_detected: |-
|
891
|
+
The `%{binary}` binary appears to not be in the PATH of the guest. This
|
892
|
+
could be because the PATH is not properly setup or perhaps chef is not
|
893
|
+
installed on this guest. Chef provisioning can not continue without
|
894
|
+
chef properly installed.
|
895
|
+
server_url_required: |-
|
896
|
+
Chef server provisioning requires that the `config.chef.chef_server_url` be set to the
|
897
|
+
URL of your chef server. Examples include "http://12.12.12.12:4000" and
|
898
|
+
"http://myserver.com:4000" (the port of course can be different, but 4000 is the default)
|
899
|
+
server_validation_key_required: |-
|
900
|
+
Chef server provisioning requires that the `config.chef.validation_key_path` configuration
|
901
|
+
be set to a path on your local machine of the validation key used to register the
|
902
|
+
VM with the chef server.
|
903
|
+
server_validation_key_doesnt_exist: |-
|
904
|
+
The validation key set for `config.chef.validation_key_path` does not exist! This
|
905
|
+
file needs to exist so it can be uploaded to the virtual machine.
|
906
|
+
|
907
|
+
puppet:
|
908
|
+
not_detected: |-
|
909
|
+
The `%{binary}` binary appears to not be in the PATH of the guest. This
|
910
|
+
could be because the PATH is not properly setup or perhaps Puppet is not
|
911
|
+
installed on this guest. Puppet provisioning can not continue without
|
912
|
+
Puppet properly installed.
|
913
|
+
running_puppet: "Running Puppet with %{manifest}..."
|
914
|
+
manifest_missing: |-
|
915
|
+
The configured Puppet manifest is missing. Please specify a path to an
|
916
|
+
existing manifest:
|
917
|
+
|
918
|
+
%{manifest}
|
919
|
+
manifests_path_missing: "The manifests path specified for Puppet does not exist: %{path}"
|
920
|
+
missing_shared_folders: |-
|
921
|
+
Shared folders that Puppet requires are missing on the virtual machine.
|
922
|
+
This is usually due to configuration changing after already booting the
|
923
|
+
machine. The fix is to run a `vagrant reload` so that the proper shared
|
924
|
+
folders will be prepared and mounted on the VM.
|
925
|
+
module_path_missing: "The configured module path doesn't exist: %{path}"
|
926
|
+
|
927
|
+
puppet_server:
|
928
|
+
not_detected: |-
|
929
|
+
The `%{binary}` binary appears to not be in the PATH of the guest. This
|
930
|
+
could be because the PATH is not properly setup or perhaps Puppet is not
|
931
|
+
installed on this guest. Puppet provisioning can not continue without
|
932
|
+
Puppet properly installed.
|
933
|
+
running_puppetd: "Running Puppet agent..."
|
934
|
+
|
935
|
+
shell:
|
936
|
+
args_not_string: "Shell provisioner `args` must be a string."
|
937
|
+
path_and_inline_set: "Only one of `path` or `inline` may be set."
|
938
|
+
no_path_or_inline: "One of `path` or `inline` must be set."
|
939
|
+
path_invalid: "`path` for shell provisioner does not exist on the host system: %{path}"
|
940
|
+
upload_path_not_set: "`upload_path` must be set for the shell provisioner."
|
941
|
+
|
942
|
+
guest:
|
943
|
+
base:
|
944
|
+
unsupported_configure_networks: |-
|
945
|
+
Networking features require support that is dependent on the operating
|
946
|
+
system running within the guest virtual machine. Vagrant has built-in support
|
947
|
+
for many operating systems: Debian, Ubuntu, Gentoo, and RedHat. The distro
|
948
|
+
of your VM couldn't be detected or doesn't support networking features.
|
949
|
+
|
950
|
+
Most of the time this is simply due to the fact that no one has contributed
|
951
|
+
back the logic necessary to set this up. Please report a bug as well as the
|
952
|
+
box you're using.
|
953
|
+
unsupported_host_name: |-
|
954
|
+
Setting host name is currently only supported on Debian, Ubuntu and RedHat.
|
955
|
+
If you'd like your guest OS to be supported, please open a ticket on the
|
956
|
+
project.
|
957
|
+
unsupported_nfs: |-
|
958
|
+
Vagrant doesn't support mounting NFS shared folders for your specific
|
959
|
+
guest operating system yet, or possibly couldn't properly detect the
|
960
|
+
operating system on the VM.
|
961
|
+
|
962
|
+
Most of the time this is simply due to the fact that no one has contributed
|
963
|
+
back the logic necessary to set this up. Please report a bug as well as the
|
964
|
+
box you're using.
|
965
|
+
unsupported_halt: |-
|
966
|
+
Vagrant doesn't support graceful shutdowns for your specific
|
967
|
+
guest operating system yet, or possibly couldn't properly detect the
|
968
|
+
operating system on the VM.
|
969
|
+
|
970
|
+
Most of the time this is simply due to the fact that no one has contributed
|
971
|
+
back the logic necessary to set this up. Please report a bug as well as the
|
972
|
+
box you're using.
|
973
|
+
unsupported_shared_folder: |-
|
974
|
+
Vagrant doesn't support mounting shared folders for your specific
|
975
|
+
guest operating system yet, or possibly couldn't properly detect the
|
976
|
+
operating system on the VM.
|
977
|
+
|
978
|
+
Most of the time this is simply due to the fact that no one has contributed
|
979
|
+
back the logic necessary to set this up. Please report a bug as well as the
|
980
|
+
box you're using.
|
981
|
+
linux:
|
982
|
+
guestpath_expand_fail: |-
|
983
|
+
Vagrant failed to determine the shell expansion of the guest path
|
984
|
+
for one of your shared folders. This is an extremely rare error case
|
985
|
+
and most likely indicates an unusual configuration of the guest system.
|
986
|
+
Please report a bug with your Vagrantfile.
|
987
|
+
mount_fail: "Failed to mount shared folders. `vboxsf` was not available."
|
988
|
+
mount_nfs_fail: |-
|
989
|
+
Mounting NFS shared folders failed. This is most often caused by the NFS
|
990
|
+
client software not being installed on the guest machine. Please verify
|
991
|
+
that the NFS client software is properly installed, and consult any resources
|
992
|
+
specific to the linux distro you're using for more information on how to
|
993
|
+
do this.
|