-
Notifications
You must be signed in to change notification settings - Fork 4.4k
/
Copy pathen.yml
3006 lines (2723 loc) · 141 KB
/
en.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
en:
vagrant:
alert: |-
[%{date}]:
%{message}
- %{url}
boot_completed: |-
Machine booted and ready!
boot_waiting: |-
Waiting for machine to boot. This may take a few minutes...
box_auto_adding: |-
Box '%{name}' could not be found. Attempting to find and install...
box_add_choose_provider: |-
This box can work with multiple providers! The providers that it
can work with are listed below. Please review the list and choose
the provider you will be working with.
%{options}
Enter your choice:
box_add_choose_provider_again: |-
Invalid choice. Try again:
box_add_with_version: |-
Adding box '%{name}' (v%{version}) for provider: %{providers}
box_added: |-
Successfully added box '%{name}' (v%{version}) for '%{provider}'!
box_adding_direct: |-
Box file was not detected as metadata. Adding it directly...
box_add_url_warn: |-
It looks like you attempted to add a box with a URL for the name...
Instead, use box_url instead of box for box URLs.
box_downloading: |-
Downloading: %{url}
box_download_error: |-
Error downloading: %{message}
box_unpacking: |-
Unpacking necessary files from: %{url}
box_expanding_url: |-
URL: %{url}
box_loading_metadata: |-
Loading metadata for box '%{name}'
box_malformed_continue_on_update: |-
Could not determine box updates because box metadata was malformed.
Vagrant will continue on...
box_outdated: |-
* '%{name}' for '%{provider}' is outdated! Current: %{current}. Latest: %{latest}
box_outdated_checking_with_refresh: |-
Checking if box '%{name}' version '%{version}' is up to date...
box_outdated_local: |-
A newer version of the box '%{name}' is available and already
installed, but your Vagrant machine is running against
version '%{old}'. To update to version '%{new}',
destroy and recreate your machine.
box_outdated_metadata_download_error: |-
There was a problem while downloading the metadata for your box
to check for updates. This is not an error, since it is usually due
to temporary network problems. This is just a warning. The problem
encountered was:
%{message}
If you want to check for box updates, verify your network connection
is valid and try again.
box_outdated_metadata_error_single: |-
Error loading box metadata while attempting to check for
updates: %{message}
box_outdated_single: |-
A newer version of the box '%{name}' for provider '%{provider}' is
available! You currently have version '%{current}'. The latest is version
'%{latest}'. Run `vagrant box update` to update.
box_outdated_metadata_error: |-
* '%{name}' for '%{provider}': Error loading metadata: %{message}
box_outdated_no_metadata: |-
* '%{name}' for '%{provider}' wasn't added from a catalog, no version information
box_updating: |-
Updating '%{name}' with provider '%{provider}' from version
'%{old}' to '%{new}'...
box_update_checking: |-
Checking for updates to '%{name}'
box_up_to_date: |-
* '%{name}' for '%{provider}' (v%{version}) is up to date
box_up_to_date_single: |-
Box '%{name}' (v%{version}) is running the latest version.
box_version_malformed:
Invalid version '%{version}' for '%{box_name}', ignoring...
cfengine_bootstrapping: |-
Bootstrapping CFEngine with policy server: %{policy_server}...
cfengine_bootstrapping_policy_hub: |-
Performing additional bootstrap for policy hubs...
cfengine_cant_detect: |-
Vagrant doesn't support detecting whether CFEngine is installed
for the guest OS running in the machine. Vagrant will assume it is
installed and attempt to continue.
cfengine_detected_ip: |-
Detected policy server IP address: %{address}...
cfengine_installing: |-
Installing CFEngine onto machine...
cfengine_installing_files_path: |-
Copying the 'files_path' files...
cfengine_no_bootstrap: |-
CFEngine doesn't require bootstrap. Not bootstrapping.
cfengine_single_run: |-
CFEngine running in "single run" mode. Will execute one file.
cfengine_single_run_execute: |-
Executing run file for CFEngine...
chef_cant_detect: |-
Vagrant does not support detecting whether Chef is installed
for the guest OS running in the machine. Vagrant will assume it is
installed and attempt to continue.
chef_already_installed: |-
Detected Chef (%{version}) is already installed
chef_installing: |-
Installing Chef (%{version})...
chef_client_cleanup_failed: |-
Cleaning up the '%{deletable}' for Chef failed. The stdout and
stderr are shown below. Vagrant will continue destroying the machine,
so please clean up these resources manually.
stdout: %{stdout}
stderr: %{stderr}
chef_config_knife_not_found: |-
The `knife` application was not found! This is required by Vagrant
to automatically delete Chef nodes and clients.
chef_run_list_empty: |-
Warning: Chef run list is empty. This may not be what you want.
cli_interrupt: |-
Exiting due to interrupt.
cloud_init_waiting: Waiting for cloud init to finish running
container_pulling_single: |-
-- Image: %{name}
container_building_single: |-
-- Path: %{path}
container_running: |-
-- Container: %{name}
container_restarting_container_args: |-
-- Detected changes to container '%{name}' args, restarting...
container_restarting_container_image: |-
-- Detected newer image for container '%{name}', restarting...
docker_auto_start_not_available: |-
Unable to configure automatic restart of Docker containers on
the guest machine
docker_cant_detect: |-
Vagrant doesn't support detecting whether Docker is installed
for the guest OS running in the machine. Vagrant will assume it is
installed and attempt to continue.
docker_configure_autostart: |-
Configuring Docker to autostart containers...
docker_installing: |-
Installing Docker onto machine...
docker_pulling_images:
Pulling Docker images...
docker_pulling_single: |-
-- Image: %{name}
docker_building_single: |-
-- Path: %{path}
docker_building_images:
Building Docker images...
docker_running: |-
-- Container: %{name}
docker_restarting_container_args: |-
-- Detected changes to container '%{name}' args, restarting...
docker_restarting_container_image: |-
-- Detected newer image for container '%{name}', restarting...
docker_starting_containers: |-
Starting Docker containers...
hyperv_enable_enhanced_session: |-
Setting VM Enhanced session transport type to HvSocket
hyperv_disable_enhanced_session: |-
Setting VM Enhanced session transport type to disabled/default (VMBus)
inserted_key: |-
Key inserted! Disconnecting and reconnecting using new SSH key...
inserting_insecure_detected: |-
Vagrant insecure key detected. Vagrant will automatically replace
this with a newly generated keypair for better security.
inserting_random_key: |-
Inserting generated public key within guest...
inserting_remove_key: |-
Removing insecure key from the guest if it's present...
installing_provider: |-
Provider '%{provider}' not found. We'll automatically install it now...
installing_provider_detail: |-
The installation process will start below. Human interaction may be
required at some points. If you're uncomfortable with automatically
installing this provider, you can safely Ctrl-C this process and install
it manually.
list_commands: |-
Below is a listing of all available Vagrant commands and a brief
description of what they do.
%{list}
moved_cwd: |-
This machine used to live in %{old_wd} but it's now at %{current_wd}.
Depending on your current provider you may need to change the name of
the machine to run it as a different machine.
guest_deb_installing_smb: |-
Installing SMB "mount.cifs"...
global_status_footer: |-
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date (use "vagrant global-status --prune" to prune invalid
entries). To interact with any of the machines, you can go to that
directory and run Vagrant, or you can use the ID directly with
Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"
global_status_none: |-
There are no active Vagrant environments on this computer! Or,
you haven't destroyed and recreated Vagrant environments that were
started with an older version of Vagrant.
plugin_needs_reinstall: |-
The following plugins were installed with a version of Vagrant
that had different versions of underlying components. Because
these component versions were changed (which rarely happens),
the plugins must be uninstalled and reinstalled.
To ensure that all the dependencies are properly updated as well
it is _highly recommended_ to do a `vagrant plugin uninstall`
prior to reinstalling.
This message will not go away until all the plugins below are
either uninstalled or uninstalled then reinstalled.
The plugins below will not be loaded until they're uninstalled
and reinstalled:
%{names}
post_up_message: |-
Machine '%{name}' has a post `vagrant up` message. This is a message
from the creator of the Vagrantfile, and not from Vagrant itself:
%{message}
provisioner_cleanup: |-
Running cleanup tasks for '%{name}' provisioner...
rsync_auto_initial: |-
Doing an initial rsync...
rsync_auto_new_folders: |-
New synced folders were added to the Vagrantfile since running
`vagrant reload`. If these new synced folders are backed by rsync,
they won't be automatically synced until a `vagrant reload` is run.
rsync_auto_no_paths: |-
There are no paths to watch! This is either because you have no
synced folders using rsync, or any rsync synced folders you have
have specified `rsync_auto` to be false.
rsync_auto_path: |-
Watching: %{path}
rsync_auto_remove_folder: |-
Not syncing %{folder} as it is not part of the current working directory.
rsync_auto_rsync_error: |-
There was an error while executing rsync. The error is shown below.
This may not be critical since rsync sometimes fails, but if this message
repeats, then please fix the issue:
%{message}
rsync_auto_post_command_error: |-
There was an error while executing the rsync post command. This error is
shown below. This may not be critical but if this message repeats please
fix the issue:
%{message}
rsync_communicator_not_ready: |-
The machine is reporting that it is not ready for rsync to
communicate with it. Verify that this machine is properly running.
rsync_communicator_not_ready_callback: |-
Failed to connect to remote machine. This is usually caused by the
machine rebooting or being halted. Please make sure the machine is
running, and modify a file to try again.
rsync_folder: |-
Rsyncing folder: %{hostpath} => %{guestpath}
rsync_folder_excludes: " - Exclude: %{excludes}"
rsync_installing: "Installing rsync to the VM..."
rsync_proxy_machine: |-
The provider ('%{provider}') for the machine '%{name}' is
using a proxy machine. RSync will sync to this proxy
instead of directly to the environment itself.
rsync_showing_output: "Showing rsync output..."
rsync_ssh_password: |-
The machine you're rsyncing folders to is configured to use
password-based authentication. Vagrant can't script rsync to automatically
enter this password, so you'll likely be prompted for a password
shortly.
If you don't want to have to do this, please enable automatic
key insertion using `config.ssh.insert_key`.
ssh_exec_password: |-
The machine you're attempting to SSH into is configured to use
password-based authentication. Vagrant can't script entering the
password for you. If you're prompted for a password, please enter
the same password you have configured in the Vagrantfile.
stdin_cant_hide_input: |-
Error! Your console doesn't support hiding input. We'll ask for
input again below, but we WILL NOT be able to hide input. If this
is a problem for you, ctrl-C to exit and fix your stdin.
up_no_machines: |-
No machines to bring up. This is usually because all machines are
set to `autostart: false`, which means you have to explicitly specify
the name of the machine to bring up.
upgrading_home_path_v1_5: |-
Vagrant is upgrading some internal state for the latest version.
Please do not quit Vagrant at this time. While upgrading, Vagrant
will need to copy all your boxes, so it will use a considerable
amount of disk space. After it is done upgrading, the temporary disk
space will be freed.
Press ctrl-c now to exit if you want to remove some boxes or free
up some disk space.
Press the Enter or Return key to continue.
trigger:
on_error_continue: |-
Trigger configured to continue on error...
abort: |-
Vagrant has been configured to abort. Terminating now...
abort_threaded: |-
Vagrant has been configured to abort. Vagrant will terminate
after remaining running actions have completed...
start: |-
Running %{type} triggers %{stage} %{name} ...
fire_with_name: |-
Running trigger: %{name}...
fire: |-
Running trigger...
run:
inline: |-
Running local: Inline script
%{command}
script: |-
Running local script: %{path}
version_current: |-
Installed Version: %{version}
version_latest: |-
Latest Version: %{version}
version_latest_installed: |-
You're running an up-to-date version of Vagrant!
version_no_checkpoint: |-
Vagrant was unable to check for the latest version of Vagrant.
Please check manually at https://www.vagrantup.com
version_upgrade_available: |-
A new version of Vagrant is available: %{latest_version} (installed version: %{installed_version})!
To upgrade visit: https://www.vagrantup.com/downloads.html
version_upgrade_howto: |-
To upgrade to the latest version, visit the downloads page and
download and install the latest version of Vagrant from the URL
below:
https://www.vagrantup.com/downloads.html
If you're curious what changed in the latest release, view the
CHANGELOG below:
https://github.com/hashicorp/vagrant/blob/v%{version}/CHANGELOG.md
cfengine_config:
classes_array: |-
The 'classes' configuration must be an array.
files_path_not_directory: |-
The 'files_path' must point to a valid directory.
invalid_mode: |-
The mode must be 'bootstrap' or 'single_run'
policy_server_address: |-
The policy server address must be set for bootstrapping.
run_file_not_found: |-
The 'run_file' specified could not be found.
virtualbox:
checking_guest_additions: |-
Checking for guest additions in VM...
network_adapter: |-
Adapter %{adapter}: %{type}%{extra}
config:
id_in_pre_import: |-
The ':id' parameter is not available in "pre-import" customizations.
intnet_on_bad_type: |-
VirtualBox internal networks can only be enabled on "private_network"
invalid_event: |-
%{event} is not a valid event for customization. Valid events
are: %{valid_events}
warning:
shared_folder_symlink_create: |-
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:
https://www.virtualbox.org/manual/ch04.html#sharedfolders
This option can be disabled globally with an environment variable:
VAGRANT_DISABLE_VBOXSYMLINKCREATE=1
or on a per folder basis within the Vagrantfile:
config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
general:
batch_notify_error: |-
An error occurred. The error will be shown after all tasks complete.
batch_unexpected_error: |-
An unexpected error occurred when executing the action on the
'%{machine}' machine. Please report this as a bug:
%{message}
batch_vagrant_error: |-
An error occurred while executing the action on the '%{machine}'
machine. Please handle this error then try again:
%{message}
config_upgrade_messages: |-
There were warnings and/or errors while loading your Vagrantfile
for the machine '%{name}'.
Your Vagrantfile was written for an earlier version of Vagrant,
and while Vagrant does the best it can to remain backwards
compatible, there are some cases where things have changed
significantly enough to warrant a message. These messages are
shown below.
%{output}
experimental:
all: |-
You have enabled the experimental flag with all features enabled.
Please use with caution, as some of the features may not be fully
functional yet.
features: |-
You have requested to enabled the experimental flag with the following features:
Features: %{features}
Please use with caution, as some of the features may not be fully
functional yet.
not_in_installer: |-
You appear to be running Vagrant outside of the official installers.
Note that the installers are what ensure that Vagrant has all required
dependencies, and Vagrant assumes that these dependencies exist. By
running outside of the installer environment, Vagrant may not function
properly. To remove this warning, install Vagrant using one of the
official packages from vagrantup.com.
upgraded_v1_dotfile: |-
A Vagrant 1.0.x state file was found for this environment. Vagrant has
gone ahead and auto-upgraded this to the latest format. Everything
should continue working as normal. Beware, however, that older versions
of Vagrant may no longer be used with this environment.
However, in case anything went wrong, the old dotfile was backed up
to the location below. If everything is okay, it is safe to remove
this backup.
Backup: %{backup_path}
plugins:
local:
uninstalled_plugins: |-
Vagrant has detected project local plugins configured for this
project which are not installed.
%{plugins}
request_plugin_install: |-
Install local plugins (Y/N)
install_rerun_command: |-
Vagrant has completed installing local plugins for the current Vagrant
project directory. Please run the requested command again.
install_all: |-
Vagrant will now install the following plugins to the local project
which have been defined in current Vagrantfile:
%{plugins}
Press ctrl-c to cancel...
#-------------------------------------------------------------------------------
# Translations for exception classes
#-------------------------------------------------------------------------------
errors:
active_machine_with_different_provider: |-
An active machine was found with a different provider. Vagrant
currently allows each machine to be brought up with only a single
provider at a time. A future version will remove this limitation.
Until then, please destroy the existing machine to up with a new
provider.
Machine name: %{name}
Active provider: %{active_provider}
Requested provider: %{requested_provider}
alias_invalid_error: |-
The defined alias is not valid. Please review the information below
to help resolve the issue:
Alias: %{alias}
Message: %{message}
batch_multi_error: |-
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.
%{message}
box_add_no_matching_provider: |-
The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.
If you're adding a box from HashiCorp's Vagrant Cloud, make sure the box is
released.
Name: %{name}
Address: %{url}
Requested provider: %{requested}
box_add_no_matching_version: |-
The box you're attempting to add has no available version that
matches the constraints you requested. Please double-check your
settings. Also verify that if you specified version constraints,
that the provider you wish to use is available for these constraints.
Box: %{name}
Address: %{url}
Constraints: %{constraints}
Available versions: %{versions}
box_add_short_not_found: |-
The box '%{name}' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: %{url}
Error: %{error}
boot_bad_state: |-
The guest machine entered an invalid state while waiting for it
to boot. Valid states are '%{valid}'. The machine is in the
'%{invalid}' state. Please verify everything is configured
properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.
boot_timeout: |-
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
box_add_exists: |-
The box you're attempting to add already exists. Remove it before
adding it again or add it with the `--force` flag.
Name: %{name}
Provider: %{provider}
Version: %{version}
box_add_direct_version: |-
You specified a box version constraint with a direct box file
path. Box version constraints only work with boxes from Vagrant
Cloud or a custom box host. Please remove the version constraint
and try again.
box_add_metadata_multi_url: |-
Multiple URLs for a box can't be specified when adding
versioned boxes. Please specify a single URL to the box
metadata (JSON) information. The full list of URLs you
specified is shown below:
%{urls}
box_add_name_mismatch: |-
The box you're adding has a name different from the name you
requested. For boxes with metadata, you cannot override the name.
If you're adding a box using `vagrant box add`, don't specify
the `--name` parameter. If the box is being added via a Vagrantfile,
change the `config.vm.box` value to match the name below.
Requested name: %{requested_name}
Actual name: %{actual_name}
box_add_name_required: |-
A name is required when adding a box file directly. Please pass
the `--name` parameter to `vagrant box add`. See
`vagrant box add -h` for more help.
box_checksum_invalid_type: |-
The specified checksum type is not supported by Vagrant: %{type}.
Vagrant supports the following checksum types:
%{types}
box_checksum_mismatch: |-
The checksum of the downloaded box did not match the expected
value. Please verify that you have the proper URL setup and that
you're downloading the proper file.
Expected: %{expected}
Received: %{actual}
box_config_changing_box: |-
While loading the Vagrantfile, the provider override specified
a new box. This box, in turn, specified a different box. This isn't
allowed, as it could lead to infinite recursion of Vagrant configuration
loading. Please fix this.
box_file_not_exist: |-
The file you are attempting to upload does not exist. Please recheck
that the file exists and was passed in correctly.
File: %{file}
box_metadata_corrupted: |-
The metadata associated with the box '%{name}' appears corrupted.
This is most often caused by a disk issue or system crash. Please
remove the box, re-add it, and try again.
box_metadata_download_error: |-
There was an error while downloading the metadata for this box.
The error message is shown below:
%{message}
box_metadata_file_not_found: |-
The "metadata.json" file for the box '%{name}' was not found.
Boxes require this file in order for Vagrant to determine the
provider it was made for. If you made the box, please add a
"metadata.json" file to it. If someone else made the box, please
notify the box creator that the box is corrupt. Documentation for
box file format can be found at the URL below:
https://www.vagrantup.com/docs/boxes/format.html
box_metadata_malformed: |-
The metadata for the box was malformed. The exact error
is shown below. Please contact the maintainer of the box so
that this issue can be fixed.
%{error}
box_metadata_malformed_version: |-
A version of the box you're loading is formatted in a way that
Vagrant cannot parse: '%{version}'. Please reformat the version
to be properly formatted. It should be in the format of
X.Y.Z.
box_not_found: |-
The box '%{name}' does not exist. Please double check and
try again. You can see the boxes that are installed with
`vagrant box list`.
box_not_found_with_provider: |-
The box '%{name}' isn't installed for the provider '%{provider}'.
Please double-check and try again. The installed providers for
the box are shown below:
%{providers}
box_not_found_with_provider_and_version: |-
The box '%{name}' (v%{version}) with provider '%{provider}'
could not be found. Please double check and try again. You
can see all the boxes that are installed with `vagrant box list`.
box_provider_doesnt_match: |-
The box you attempted to add doesn't match the provider you specified.
Provider expected: %{expected}
Provider of box: %{actual}
box_remove_multi_provider: |-
You requested to remove the box '%{name}'. This box has
multiple providers. You must explicitly select a single
provider to remove with `--provider`.
Available providers: %{providers}
box_remove_multi_version: |-
You requested to remove the box '%{name}' with provider
'%{provider}'. This box has multiple versions. You must
explicitly specify which version you want to remove with
the `--box-version` flag or specify the `--all` flag to remove all
versions. The available versions for this box are:
%{versions}
box_remove_not_found: |-
The box you requested to be removed could not be found. No
boxes named '%{name}' could be found.
box_remove_provider_not_found: |-
You requested to remove the box '%{name}' with provider
'%{provider}'. The box '%{name}' exists but not with
the provider specified. Please double-check and try again.
The providers for this are: %{providers}
box_remove_version_not_found: |-
You requested to remove the box '%{name}' version '%{version}' with
provider '%{provider}', but that specific version of the box is
not installed. Please double-check and try again. The available versions
for this box are:
%{versions}
box_server_not_set: |-
A URL to a Vagrant Cloud server is not set, so boxes cannot be added with a
shorthand ("mitchellh/precise64") format. You may also be seeing this
error if you meant to type in a path to a box file which doesn't exist
locally on your system.
To set a URL to a Vagrant Cloud server, set the `VAGRANT_SERVER_URL`
environmental variable. Or, if you meant to use a file path, make sure
the path to the file is valid.
box_update_multi_provider: |-
You requested to update the box '%{name}'. This box has
multiple providers. You must explicitly select a single
provider to remove with `--provider`.
Available providers: %{providers}
box_update_no_box: |-
Box '%{name}' not installed, can't check for updates.
box_update_no_metadata: |-
The box '%{name}' is not a versioned box. The box was added
directly instead of from a box catalog. Vagrant can only
check the versions of boxes that were added from a catalog
such as from the public Vagrant Server.
box_update_no_name: |-
This machine doesn't have a box. Won't update anything.
bundler_disabled: |-
Vagrant's built-in bundler management mechanism is disabled because
Vagrant is running in an external bundler environment. In these
cases, plugin management does not work with Vagrant. To install
plugins, use your own Gemfile. To load plugins, either put the
plugins in the `plugins` group in your Gemfile or manually require
them in a Vagrantfile.
bundler_error: |-
Vagrant failed to properly resolve required dependencies. These
errors can commonly be caused by misconfigured plugin installations
or transient network issues. The reported error is:
%{message}
source_spec_not_found: |-
Vagrant failed to properly initialize its internal library
dependencies. Please try running the command again. If this
error persists, please report a bug.
cant_read_mac_addresses: |-
The provider you are using ('%{provider}') doesn't support the
"nic_mac_addresses" provider capability which is required
for advanced networking to work with this guest OS. Please inform
the author of the provider to add this feature.
Until then, you must remove any networking configurations other
than forwarded ports from your Vagrantfile for Vagrant to continue.
capability_host_explicit_not_detected: |-
The explicit capability host specified of '%{value}' could not be
found.
This is an internal error that users should never see. Please report
a bug.
capability_host_not_detected: |-
The capability host could not be detected. This is an internal error
that users should never see. Please report a bug.
capability_invalid: |-
The capability '%{cap}' is invalid. This is an internal error that
users should never see. Please report a bug.
capability_not_found: |-
The capability '%{cap}' could not be found. This is an internal error
that users should never see. Please report a bug.
cfengine_bootstrap_failed: |-
Failed to bootstrap CFEngine. Please see the output above to
see what went wrong and address the issue.
cfengine_cant_autodetect_ip: |-
Vagrant was unable to automatically detect the IP address of the
running machine to use as the policy server address. Please specify
the policy server address manually, or verify that the networks are
configured properly internally.
cfengine_install_failed: |-
After installing CFEngine, Vagrant still can't detect a proper
CFEngine installation. Please verify that CFEngine was properly
installed, as the installation may have failed.
cfengine_not_installed: |-
CFEngine appears not to be installed on the guest machine. Vagrant
can attempt to install CFEngine for you if you set the "install"
setting to "true", but this setting was not set. Please install
CFEngine on the guest machine or enable the "install" setting for
Vagrant to attempt to install it for you.
cli_invalid_options: |-
An invalid option was specified. The help for this command
is available below.
%{help}
cli_invalid_usage: |-
This command was not invoked properly. The help for this command is
available below.
%{help}
clone_not_found: |-
The specified Vagrantfile to clone from was not found. Please verify
the `config.vm.clone` setting points to a valid Vagrantfile.
clone_machine_not_found: |-
The clone environment hasn't been created yet. To clone from
another Vagrantfile, it must already be created with `vagrant up`.
It doesn't need to be running.
Additionally, the created environment must be started with a provider
matching this provider. For example, if you're using VirtualBox,
the clone environment must also be using VirtualBox.
cloud_init_not_found: |-
cloud-init is not found. Please ensure that cloud-init is installed and
available on path for guest '%{guest_name}'.
cloud_init_command_failed: |-
cloud init command '%{cmd}' failed on guest '%{guest_name}'.
command_deprecated: |-
The command 'vagrant %{name}' has been deprecated and is no longer functional
within Vagrant.
command_suspend_all_arguments: |-
The suspend command with the `--all-global` flag does not take any arguments.
command_unavailable: |-
The executable '%{file}' Vagrant is trying to run was not
found in the PATH variable. This is an error. Please verify
this software is installed and on the path.
command_unavailable_windows: |-
The executable '%{file}' Vagrant is trying to run was not
found in the %PATH% variable. This is an error. Please verify
this software is installed and on the path.
communicator_not_found: |-
The requested communicator '%{comm}' could not be found.
Please verify the name is correct and try again.
config_invalid: |-
There are errors in the configuration of this machine. Please fix
the following errors and try again:
%{errors}
config_upgrade_errors: |-
Because there were errors upgrading your Vagrantfiles, Vagrant
can no longer continue. Please fix the errors above and try again.
copy_private_key_failed: |-
Vagrant failed to copy the default insecure private key into your
home directory. This is usually caused by a permissions error.
Please make sure the permissions of the source is readable and
the destination is writable.
Source: %{source}
Destination: %{destination}
corrupt_machine_index: |-
The machine index which stores all required information about
running Vagrant environments has become corrupt. This is usually
caused by external tampering of the Vagrant data folder.
Vagrant cannot manage any Vagrant environments if the index is
corrupt. Please attempt to manually correct it. If you are unable
to manually correct it, then remove the data file at the path below.
This will leave all existing Vagrant environments "orphaned" and
they'll have to be destroyed manually.
Path: %{path}
create_iso_host_cap_not_found: |-
Vagrant cannot create an iso due to the host capability for creating isos not existing.
Vagrant will now exit.
destroy_requires_force: |-
Destroy doesn't have a TTY to ask for confirmation. Please pass the
`--force` flag to force a destroy, otherwise attach a TTY so that
the destroy can be confirmed.
dotfile_upgrade_json_error: |-
A Vagrant 1.0.x local state file was found. Vagrant is able to upgrade
this to the latest format automatically, however various checks are
put in place to verify data isn't incorrectly deleted. In this case,
the old state file was not valid JSON. Vagrant 1.0.x would store state
as valid JSON, meaning that this file was probably tampered with or
manually edited. Vagrant's auto-upgrade process cannot continue in this
case.
In most cases, this can be resolve by simply removing the state file.
Note however though that if Vagrant was previously managing virtual
machines, they may be left in an "orphan" state. That is, if they are
running or exist, they'll have to manually be removed.
If you're unsure what to do, ask the Vagrant mailing list or contact
support.
State file path: %{state_file}
downloader_error: |-
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
%{message}
downloader_interrupted: |-
The download was interrupted by an external signal. It did not
complete.
downloader_checksum_error: |-
The calculated checksum of the requested file does not match the expected
checksum!
File source: %{source}
Checksum type: %{type}
Expected checksum: %{expected_checksum}
Calculated checksum: %{actual_checksum}
env_inval: |-
Vagrant received an "EINVAL" error while attempting to set some
environment variables. This is usually caused by the total size of your
environment variables being too large. Vagrant sets a handful of
environment variables to function and requires this to work. Please
delete some environment variables prior to executing Vagrant to
fix this.
environment_locked: |-
Vagrant attempted to acquire a lock named '%{name}', but this
lock is being held by another instance of Vagrant already. Please
wait and try again.
environment_non_existent_cwd: |-
The working directory for Vagrant doesn't exist! This is the
specified working directory:
%{cwd}
forward_port_adapter_not_found: |-
The adapter to attach a forwarded port to was not found. Please
verify that the given adapter is setup on the machine as a NAT
interface.
Host port: %{host}
Guest port: %{guest}
Adapter: %{adapter}
freebsd_nfs_whitespace: |-
FreeBSD hosts do not support sharing directories with whitespace in
their path. Please adjust your path accordingly.
guest_capability_invalid: |-
The registered guest capability '%{cap}' for the
detected guest OS '%{guest}' is invalid. The capability does
not implement the proper method. This is a bug with Vagrant or the
plugin that implements this capability. Please report a bug.
guest_capability_not_found: |-
Vagrant attempted to execute the capability '%{cap}'
on the detect guest OS '%{guest}', but the guest doesn't
support that capability. This capability is required for your
configuration of Vagrant. Please either reconfigure Vagrant to
avoid this capability or fix the issue by creating the capability.
guest_explicit_not_detected: |-
The guest implementation explicitly specified in your Vagrantfile
("%{value}") could not be found. Please verify that the plugin is
installed which implements this guest and that the value you
used for `config.vm.guest` is correct.
guest_not_detected: |-
The guest operating system of the machine could not be detected!
Vagrant requires this knowledge to perform specific tasks such
as mounting shared folders and configuring networks. Please add
the ability to detect this guest operating system to Vagrant
by creating a plugin or reporting a bug.
home_dir_later_version: |-
It appears that a newer version of Vagrant was run on this machine
at some point. The current version of Vagrant is unable to read
the configuration structure of this newer version. Please upgrade to
the latest version of Vagrant.
home_dir_not_accessible: |-
The home directory you specified is not accessible. The home
directory that Vagrant uses must be both readable and writable.
You specified: %{home_path}
home_dir_unknown_version: |-
The Vagrant app data directory (%{path}) is in a
structure Vagrant doesn't understand. This is a rare exception.
Please report an issue or ask the mailing list for help.
host_explicit_not_detected: |-
The host implementation explicitly specified in your Vagrantfile
("%{value}") could not be found. Please verify that the plugin is
installed which implements this host and that the value you used
for `config.vagrant.host` is correct.
iso_build_failed: |-
Failed to build iso image. The following command returned an error:
%{cmd}
Stdout from the command:
%{stdout}
Stderr from the command:
%{stderr}
hyperv_virtualbox_error: |-
Hyper-V and VirtualBox cannot be used together and will result in a
system crash. Vagrant will now exit. Please disable Hyper-V if you wish
to use VirtualBox.
interrupted: |-
Vagrant exited after cleanup due to external interrupt.
local_data_dir_not_accessible: |-
The directory Vagrant will use to store local environment-specific
state is not accessible. The directory specified as the local data
directory must be both readable and writable for the user that is
running Vagrant.
Local data directory: %{local_data_path}
linux_mount_failed: |-
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:
%{command}
The error output from the last command was:
%{output}
linux_rdp_client_not_found: |-
An appropriate RDP client was not found. Vagrant requires either
`xfreerdp` or `rdesktop` in order to connect via RDP to the Vagrant
environment. Please ensure one of these applications is installed and
available on the path and try again.
machine_action_locked: |-
An action '%{action}' was attempted on the machine '%{name}',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this