Latest revision as of 19:57, 17 November 2019

External

Connect to machine via SSH:

vagrant ssh

How does it know to connect to the instance it was started? More about jump box.

@@ Line 7: / Line 7: @@
 * [[Vagrant#Operations|Vagrant]]
-=Plugin Operations=
+=Subjects=
-{{Internal|Vagrant Plugin Operations|Plugin Operations}}
+* <span id='Plugin_Operations'></span>[[Vagrant Plugin Operations|Plugin operations]]
-=Environment Operations=
+* <span id='Environment_Operations'></span>[[Vagrant Environment Operations|Environment operations]]
-{{Internal|Vagrant Environment Operations|Environment Operations}}
+* <span id='Instance_Operations'></span>[[Vagrant Instance Operations|Instance operations]]
+* <span id='Box_Operations'></span>[[Vagrant Box Operations|Box operations]]
+* <span id='Managing_a_VM_in_an_AWS_Environment'></span>[[Vagrant AWS Provider|Managing a VM in an AWS Environment]]
-=Box Operations=
-==List==
- vagrant box list
-=Instance Operations=
-{{Internal|Vagrant Instance Operations|Instance Operations}}
-==init==
-{{External|https://www.vagrantup.com/docs/cli/init.html}}
- vagrant init
 ==ssh==
@@ Line 37: / Line 25: @@
 More about jump box.
 </font>
-==global-status==
-Global status of the VM:
- vagrant global-status
-==status==
- vagrant status [''name''|''id'']
-==destroy==
-Stops and deletes all traces of the vagrant machine:
- vagrant destroy
- vagrant destroy [''name''|''id'']
-If the corresponding VM runs in AWS EC2, this terminates the instance.
-=Managing a VM in an AWS Environment=
-{{Internal|Vagrant AWS Provider|Vagrant AWS Provider}}