Mirrors/BastilleBSD_bastille
1
0
Fork 1
mirror of https://github.com/BastilleBSD/bastille.git synced 2025-12-11 09:29:55 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: Document -c for destroy

Browse Source
This commit is contained in:
tschettervictor
2025-02-23 09:40:08 -07:00
committed by GitHub
parent c7230ab9be
commit 2078597145
1 changed files with 14 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
docs/chapters/subcommands/destroy.rst
View File

@@ -2,26 +2,29 @@
destroy
=======
Containers can be destroyed and thrown away just as easily as they were
created. Note: containers must be stopped before destroyed.
Jails can be destroyed and thrown away just as easily as they were
created. Note: containers must be stopped before destroyed. Using
the `-a|--auto` option will automatically stop the jail before destroying it.
.. code-block:: shell
ishmael ~ # bastille stop folsom
ishmael ~ # bastille destroy -a folsom
[folsom]:
folsom: removed
.. code-block:: shell
ishmael ~ # bastille destroy folsom
Deleting Container: folsom.
Note: containers console logs not destroyed.
/usr/local/bastille/logs/folsom_console.log
Release can be destroyed provided there are no child jails. The `force` option
deletes the release cache directory as well:
Release can be destroyed provided there are no child jails. The `-c|--no-cache` option
will retain the releas cache directory, if you choose to keep it.
.. code-block:: shell
ishmael ~ # bastille destroy force 14.0-RELEASE
Deleting base: 14.0-RELEASE
ishmael ~ # bastille destroy help
Usage: bastille destroy [option(s)] [JAIL|RELEASE]
Options:
-a | --auto Auto mode. Start/stop jail(s) if required.
-f | --force Force unmount any mounted datasets when destroying a jail or release (ZFS only).
-c | --no-cache Do no destroy cache when destroying a release.
-x | --debug Enable debug mode.