From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/vagrant/cli%2Fglobal-status.html | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 devdocs/vagrant/cli%2Fglobal-status.html (limited to 'devdocs/vagrant/cli%2Fglobal-status.html') diff --git a/devdocs/vagrant/cli%2Fglobal-status.html b/devdocs/vagrant/cli%2Fglobal-status.html new file mode 100644 index 00000000..61ceeaf9 --- /dev/null +++ b/devdocs/vagrant/cli%2Fglobal-status.html @@ -0,0 +1,7 @@ +

Global Status

Command: vagrant global-status

This command will tell you the state of all active Vagrant environments on the system for the currently logged in user.

The IDs in the output that look like a1b2c3 can be used to control the Vagrant machine from anywhere on the system. Any Vagrant command that takes a target machine (such as up, halt, destroy) can be used with this ID to control it. For example: vagrant destroy a1b2c3.

Options

Environment Not Showing Up

If your environment is not showing up, you may have to do a vagrant destroy followed by a vagrant up.

If you just upgraded from a previous version of Vagrant, existing environments will not show up in global-status until they are destroyed and recreated.

+

+ © 2010–2018 Mitchell Hashimoto
Licensed under the MPL 2.0 License.
+ https://www.vagrantup.com/docs/cli/global-status.html +

+
-- cgit v1.2.3