Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Destroy release also destroys the cached release #731

Merged
merged 1 commit into from
Dec 16, 2024
Merged

Destroy release also destroys the cached release #731

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/chapters/subcommands/destroy.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
4 changes: 3 additions & 1 deletion docs/chapters/upgrading.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.