From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Thu, 14 Aug 2025 22:58:58 -0500 Subject: removing all downloaded devdocs files --- devdocs/vagrant/cli%2Fdestroy.html | 8 -------- 1 file changed, 8 deletions(-) delete mode 100644 devdocs/vagrant/cli%2Fdestroy.html (limited to 'devdocs/vagrant/cli%2Fdestroy.html') diff --git a/devdocs/vagrant/cli%2Fdestroy.html b/devdocs/vagrant/cli%2Fdestroy.html deleted file mode 100644 index 29573042..00000000 --- a/devdocs/vagrant/cli%2Fdestroy.html +++ /dev/null @@ -1,8 +0,0 @@ -

Destroy

Command: vagrant destroy [name|id]

This command stops the running machine Vagrant is managing and destroys all resources that were created during the machine creation process. After running this command, your computer should be left at a clean state, as if you never created the guest machine in the first place.

For linux-based guests, Vagrant uses the shutdown command to gracefully terminate the machine. Due to the varying nature of operating systems, the shutdown command may exist at many different locations in the guest's $PATH. It is the guest machine's responsibility to properly populate the $PATH with directory containing the shutdown command.

Options

The destroy command does not remove a box that may have been installed on your computer during vagrant up. Thus, even if you run vagrant destroy, the box installed in the system will still be present on the hard drive. To return your computer to the state as it was before vagrant up command, you need to use vagrant box remove.

For more information, read about the vagrant box remove command.

-

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

-
-- cgit v1.2.3