haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Added 'vagrant reload' info on collision_error

This commit is contained in:
Tieme van Veen 2016-05-10 10:56:22 +02:00
parent 788bd557c4
commit b8ca105602
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
templates/locales/en.yml
View File

@ -1733,7 +1733,11 @@ en:
Sometimes, Vagrant will attempt to auto-correct this for you. In this Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding. is in a state which doesn't allow modifying port forwarding. You could
try 'vagrant reload' (equivalent of running a halt followed by an up)
so vagrant can attempt to auto-correct this upon booting. Be warned
that any unsaved work might be lost.
fixed_collision: |- fixed_collision: |-
Fixed port collision for %{guest_port} => %{host_port}. Now on port %{new_port}. Fixed port collision for %{guest_port} => %{host_port}. Now on port %{new_port}.
forwarding: Forwarding ports... forwarding: Forwarding ports...