summaryrefslogtreecommitdiff
path: root/devdocs/vagrant/cli%2Fdestroy.html
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2025-08-14 22:58:58 -0500
committerCraig Jennings <c@cjennings.net>2025-08-14 22:58:58 -0500
commit82ba818ff456bcd6d56a06226e3f27e98fbb55c3 (patch)
tree158cfc17b2f644a10f063cb546752cfaae12c97f /devdocs/vagrant/cli%2Fdestroy.html
parent9278ddd4ea1a8b1a4c1edaa8894516e3f48d245b (diff)
downloaddotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.tar.gz
dotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.zip
removing all downloaded devdocs files
Diffstat (limited to 'devdocs/vagrant/cli%2Fdestroy.html')
-rw-r--r--devdocs/vagrant/cli%2Fdestroy.html8
1 files changed, 0 insertions, 8 deletions
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 @@
-<h1 id="destroy"> Destroy </h1> <p><strong>Command: <code>vagrant destroy [name|id]</code></strong></p> <p>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.</p> <p>For linux-based guests, Vagrant uses the <code>shutdown</code> command to gracefully terminate the machine. Due to the varying nature of operating systems, the <code>shutdown</code> command may exist at many different locations in the guest's <code>$PATH</code>. It is the guest machine's responsibility to properly populate the <code>$PATH</code> with directory containing the <code>shutdown</code> command.</p> <h2 id="options"> Options </h2> <ul> <li>
-<a href="#f"><code>-f</code></a> or <code>--force</code> - Do not ask for confirmation before destroying. </li> <li>
-<a href="#no-parallel"><code>--[no-]parallel</code></a> - Destroys multiple machines in parallel if the provider supports it. Please consult the provider documentation to see if this feature is supported. </li> </ul> <blockquote class="alert alert-info"> <p>The <code>destroy</code> command does not remove a box that may have been installed on your computer during <code>vagrant up</code>. Thus, even if you run <code>vagrant destroy</code>, 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 <code>vagrant up</code> command, you need to use <code>vagrant box remove</code>.</p> <p>For more information, read about the <a href="box"><code>vagrant box remove</code></a> command.</p> </blockquote><div class="_attribution">
- <p class="_attribution-p">
- &copy; 2010&ndash;2018 Mitchell Hashimoto<br>Licensed under the MPL 2.0 License.<br>
- <a href="https://www.vagrantup.com/docs/cli/destroy.html" class="_attribution-link">https://www.vagrantup.com/docs/cli/destroy.html</a>
- </p>
-</div>