From bc54c30ef110a7c77170a05e1d283c32756284b0 Mon Sep 17 00:00:00 2001 From: foudil Date: Thu, 7 Nov 2024 22:41:10 +0100 Subject: [PATCH] Document destroy force release as also destroying the cache --- docs/chapters/subcommands/destroy.rst | 8 ++++++++ docs/chapters/upgrading.rst | 4 +++- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/chapters/subcommands/destroy.rst b/docs/chapters/subcommands/destroy.rst index d8fcb8f4..f800e386 100644 --- a/docs/chapters/subcommands/destroy.rst +++ b/docs/chapters/subcommands/destroy.rst @@ -17,3 +17,11 @@ created. Note: containers must be stopped before destroyed. 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: + +.. code-block:: shell + + ishmael ~ # bastille destroy force 14.0-RELEASE + Deleting base: 14.0-RELEASE diff --git a/docs/chapters/upgrading.rst b/docs/chapters/upgrading.rst index 719f6103..b059fa0d 100644 --- a/docs/chapters/upgrading.rst +++ b/docs/chapters/upgrading.rst @@ -38,4 +38,6 @@ After upgrading all jails from one release to the next you may find that you now `bastille list releases` to list all bootstrapped releases. -`bastille destroy X.Y-RELEASE` to fully delete the release. +`bastille destroy X.Y-RELEASE` to fully delete the release. + +`bastille destroy force X.Y-RELEASE` to delete the cache directory as well.